PS3.2

The information in this publication was considered technically sound by the consensus of persons engaged in the development and approval of the document at the time it was developed. Consensus does not necessarily mean that there is unanimous agreement among every person participating in the development of this document.

NEMA standards and guideline publications, of which the document contained herein is one, are developed through a voluntary consensus standards development process. This process brings together volunteers and/or seeks out the views of persons who have an interest in the topic covered by this publication. While NEMA administers the process and establishes rules to promote fairness in the development of consensus, it does not write the document and it does not independently test, evaluate, or verify the accuracy or completeness of any information or the soundness of any judgments contained in its standards and guideline publications.

NEMA disclaims liability for any personal injury, property, or other damages of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly resulting from the publication, use of, application, or reliance on this document. NEMA disclaims and makes no guaranty or warranty, expressed or implied, as to the accuracy or completeness of any information published herein, and disclaims and makes no warranty that the information in this document will fulfill any of your particular purposes or needs. NEMA does not undertake to guarantee the performance of any individual manufacturer or seller's products or services by virtue of this standard or guide.

In publishing and making this document available, NEMA is not undertaking to render professional or other services for or on behalf of any person or entity, nor is NEMA undertaking to perform any duty owed by any person or entity to someone else. Anyone using this document should rely on his or her own independent judgment or, as appropriate, seek the advice of a competent professional in determining the exercise of reasonable care in any given circumstances. Information and other standards on the topic covered by this publication may be available from other sources, which the user may wish to consult for additional views or information not covered by this publication.

NEMA has no power, nor does it undertake to police or enforce compliance with the contents of this document. NEMA does not certify, test, or inspect products, designs, or installations for safety or health purposes. Any certification or other statement of compliance with any health or safety-related information in this document shall not be attributable to NEMA and is solely the responsibility of the certifier or maker of the statement.

Foreword

This DICOM Standard was developed according to the procedures of the DICOM Standards Committee.

The DICOM Standard is structured as a multi-part document using the guidelines established in [ISO/IEC Directives, Part 2].

1 Scope and Field of Application

Conformance Statements are critical to interoperability because they provide important information for implementers and system integrators in order to determine whether or not applications do interoperate. In addition, when issues occur, they provide a source of information in order to potentially resolve any problems. Lastly, it is important to provide potential implementers with a consistent template for generating these documents.

PS3.2 defines principles that implementations claiming conformance to the Standard shall follow. PS3.2 specifies:

the minimum general conformance requirements that must be met by any implementation claiming conformance to the DICOM Standard. Additional conformance requirements for particular features, Service Classes, Information Objects, and communications protocols may be found in the conformance sections of other Parts of the DICOM Standard;
the purpose and structure of a Conformance Statement. PS3.2 provides a framework by which conformance information can be placed into a Conformance Statement as dictated by the conformance sections of other Parts of the DICOM Standard.

The DICOM Standard does not specify:

testing or validation procedures to assess an implementation's conformance to the Standard;
testing or validation procedures to assess whether an implementation matches to its Conformance Statement;
what optional features, Service Classes, or Information Objects should be supported for a given type of device.

2 Normative References

The following standards contain provisions, which, through reference in this text, constitute provisions of this Standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this Standard are encouraged to investigate the possibilities of applying the most recent editions of the standards indicated below.

[ISO/IEC Directives, Part 2] ISO/IEC. 2016/05. 7.0. Rules for the structure and drafting of International Standards. http://www.iec.ch/members_experts/refdocs/iec/isoiecdir-2%7Bed7.0%7Den.pdf .

[ISO 7498-1] ISO. 1994. Information Processing Systems - Open Systems Interconnection - Basic Reference Model.

[ISO 8649] ISO. 1988. Information Processing Systems - Open Systems Interconnection - Service definition for the Association Control Service Element (ACSE).

[ISO 8822] ISO. 1988. Information Processing Systems - Open Systems Interconnection - Connection oriented presentation service definition.

3 Definitions

For the purposes of this Standard the following definitions apply.

3.1 Reference Model Definitions

This Part makes use of the following terms defined in [ISO 7498-1]:

Application Entity (AE): See [ISO 7498-1].
Application Entity Title: See [ISO 7498-1].
Protocol Data Unit: See [ISO 7498-1].
Transfer Syntax: See [ISO 7498-1].

3.2 ACSE Service Definitions

This Part makes use of the following terms defined in [ISO 8649]:

Association: See [ISO 8649].
Association Initiator: See [ISO 8649].

3.3 Presentation Service Definitions

This Part makes use of the following terms defined in [ISO 8822]:

Abstract Syntax: See [ISO 8822].
Abstract Syntax Name: See [ISO 8822].
Presentation Context: See [ISO 8822].
Transfer Syntax Name: See [ISO 8822].

3.4 DICOM Introduction and Overview Definitions

This Part makes use of the following terms defined in PS3.1:

Conformance Statement: See Conformance Statement in PS3.1 .
Information Object: See Information Object in PS3.1 .
Service-Object Pair Class (SOP Class): See Service-Object Pair Class in PS3.1 .

3.5 DICOM Information Object Definitions

This Part makes use of the following terms defined in PS3.3:

Information Object Definition (IOD): See Information Object Definition in PS3.3 .

3.6 DICOM Service Class Specification Definitions

This Part makes use of the following terms defined in PS3.4:

Real-World Activity: See Real-World Activity in PS3.4 .
Service Class: See Service Class in PS3.4 .
Service Class User (SCU): See Service Class User in PS3.4 .
Service Class Provider (SCP): See Service Class Provider in PS3.4 .
Meta Service-Object Pair Class (Meta SOP Class): See Meta Service-Object Pair Class in PS3.4 .

3.7 DICOM Data Structure and Encoding Definitions

This Part makes use of the following terms defined in PS3.5:

Data Set: See Data Set in PS3.5 .
DICOM Transfer Syntax: See DICOM Transfer Syntax in PS3.5 .
Unique Identifier (UID): See Unique Identifier in PS3.5 .

3.8 DICOM Message Exchange Definitions

This Part makes use of the following terms defined in PS3.7:

Extended Negotiation: See Extended Negotiation in PS3.7 .
Implementation Class UID: See Implementation Class UID in PS3.7 .

3.9 DICOM Upper Layer Service Definitions

This Part makes use of the following terms defined in PS3.8:

DICOM Upper Layer Service: See DICOM Upper Layer Service in PS3.8 .
Presentation Address: See Presentation Address in PS3.8 .

3.10 Media Storage and File Format for Data Interchange

This Part makes use of the following terms defined in PS3.10:

File-set: See File-set in PS3.10 .
File-set Creator (FSC): See File-set Creator in PS3.10 .
File-set Reader (FSR): See File-set Reader in PS3.10 .
File-set Updater (FSU): See File-set Updater in PS3.10 .
Media Storage Application Profile: See Media Storage Application Profile in PS3.10 .

3.11 DICOM Conformance

This Part uses the following definitions:

Standard SOP Class

A SOP Class defined in the DICOM Standard that is used in an implementation with no modifications.

Standard Extended SOP Class

A SOP Class defined in the DICOM Standard extended in an implementation with additional Type 3 Attributes. The additional Attributes may either be drawn from the Data Dictionary in PS3.6, or may be Private Attributes. The semantics of the related Standard SOP Class shall not be modified by the additional Type 3 Attributes when absent. Therefore, the Standard Extended SOP Class utilizes the same UID as the related Standard SOP Class.

Note

IODs from a Standard Extended SOP Class may be freely exchanged between DICOM implementations since implementations that do not recognize the additional Type 3 Attributes would simply ignore them.

Specialized SOP Class

A SOP Class derived from a Standard SOP Class that has been specialized in an implementation by additional Type 1, 1C, 2, 2C, or 3 Attributes, by enumeration of specific permitted values for Attributes, or by enumeration of specific permitted Templates. The additional Attributes may either be drawn from the Data Dictionary in PS3.6, or may be Private Attributes. The enumeration of permitted Attribute values or Templates shall be a subset of those permitted in the related Standard SOP Class. Since the semantics of the related Standard SOP Class may be modified by the additional Attributes, a Specialized SOP Class utilizes a Privately Defined UID that differs from the UID for the related Standard SOP Class.

Note

Since a Specialized SOP Class has a different UID than a Standard or Standard Extended SOP Class, other DICOM implementations may not recognize the Specialized SOP Class. Because of this limitation, a Specialized SOP Class should only be used when a Standard or Standard Extended SOP Class would not be appropriate. Before different implementations can exchange Instances in a Specialized SOP Class, the implementations must agree on the UID, content (in particular the additional Type 1, 1C, 2, and 2C Attributes), and semantics of the Specialized SOP Class. A Specialized SOP Class may be used to create a new or experimental SOP Class that is closely related to a Standard SOP Class.
The Association Negotiation for a Specialized SOP Class may include a SOP Class Common Extended Negotiation Sub-Item (as defined in PS3.7) for identification of the Service Class and of the Related General SOP Class from which it was specialized. This may allow a receiving application, without prior agreement on the Specialized SOP Class IOD, to process Instances of that class as if they were instances of a Related General SOP Class.

Private SOP Class

A SOP Class that is not defined in the DICOM Standard, but is published in an implementation's Conformance Statement.

Note

Since a Private SOP Class is not defined in the DICOM Standard, other DICOM implementations may not recognize the Private SOP Class. Because of this limitation, a Private SOP Class should only be used when a Standard or Standard Extended SOP Class would not be appropriate. In order for different implementations to exchange Instances in a Private SOP Class, the implementations must agree on the UID, content (in particular the Type 1, 1C, 2, and 2C Attributes), and semantics of the Private SOP Class. A Private SOP Class may be used to create a totally new or experimental SOP Class.

Standard Attribute

An Attribute defined in the Data Dictionary in PS3.6.

Private Attribute

An Attribute that is not defined in the DICOM Standard.

Standard Application Profile

An Application Profile defined in the DICOM Standard that is used in an implementation with no modifications.

Augmented Application Profile

An Application Profile derived from a Standard Application Profile by incorporating support for additional Standard or Standard Extended SOP Classes.

Private Application Profile

An Application Profile that is not defined in the DICOM Standard, but is published in an implementation's Conformance Statement.

Security Profile

A mechanism for selecting an appropriate set of choices from the Parts of the DICOM Standard along with corresponding security mechanisms (e.g., encryption algorithms) for the support of security facilities.

Transformation of DICOM SR to CDA

A mechanism for mapping and transforming DICOM SR objects to HL7 CDA documents.

3.12 Hypertext Transfer Protocol (HTTP/HTTPS) Definitions

This Part makes use of the following terms defined in PS3.18:

HTTP: See HTTP in PS3.18 .
HTTPS: See HTTPS in PS3.18 .
origin server: See origin server in PS3.18 .
user agent: See user agent in PS3.18 .

3.13 Web Services Definitions

This Part makes use of the following terms defined in PS3.18

Bulk Data: See Bulk Data in PS3.18 .
Bulk Data URI: See Bulk Data URI in PS3.18 .
DICOM Object: See DICOM Object in PS3.18 .
DICOM Resource: See DICOM Resource in PS3.18 .
DIMSE Proxy: See DIMSE Proxy in PS3.18 .
Event Report: See Event Report in PS3.18 .
Metadata: See Metadata in PS3.18 .
RESTful Web Service: See RESTful Web Service in PS3.18 .
Service: See Service in PS3.18 .
sRGB: See sRGB in PS3.18 .
Status Report: See Status Report in PS3.18 .
Subscriber: See Subscriber in PS3.18 .
Target URI: See Target URI in PS3.18 .
Thumbnail: See Thumbnail in PS3.18 .
Transaction: See Transaction in PS3.18 .
UTF-8: See UTF-8 in PS3.18 .

4 Symbols and Abbreviations

The following symbols and abbreviations are used in this Part.

ACR: American College of Radiology
ACSE: Association Control Service Element
AE: Application Entity
ANSI: American National Standards Institute
AP: Application Profile
API: Application Programming Interface
ASCII: American Standard Code for Information Interchange
CEN TC251: Comite Europeen de Normalisation-Technical Committee 251-Medical Informatics
DICOM: Digital Imaging and Communications in Medicine
DIMSE: DICOM Message Service Element
DIMSE-C: DICOM Message Service Element-Composite
DIMSE-N: DICOM Message Service Element-Normalized
FSC: File-set Creator
FSR: File-set Reader
FSU: File-set Updater
HISPP: Healthcare Informatics Standards Planning Panel
HL7: Health Level 7
IE: Information Entity
IEEE: Institute of Electrical and Electronics Engineers
IOD: Information Object Definition
ISO: International Standards Organization
ISP: International Standardized Profile
JIRA: Japan Medical Imaging and Radiological Systems Industries Association
MPPS: Modality Performed Procedure Step
MSDS: Healthcare Message Standard Developers Sub-Committee
NEMA: National Electrical Manufacturers Association
OSI: Open Systems Interconnection
PDU: Protocol Data Unit
QIDO-RS: Query based on ID for DICOM Objects by RESTful Services
REST: Representational State Transfer
RESTful: A RESTful Web service is a Web service implemented using REST architecture and HTTP (see http://www.ics.uci.edu/~fielding/pubs/dissertation/fielding_dissertation.pdf)
RWA: Real-World Activity
SCP: Service Class Provider
SCU: Service Class User
SOP: Service-Object Pair
STOW-RS: STore Over the Web by RESTful Services
TCP/IP: Transmission Control Protocol/Internet Protocol
UID: Unique Identifier
UML: Unified Modeling Language
WADO-RS: Web Access to DICOM Objects by RESTful Services
WADO-URI: Web Access to DICOM Objects by URI

5 Conventions

5.1 Application Data Flow Diagram

In a Conformance Statement, the relationships between Real-World Activities and Application Entities are illustrated by an Application Data Flow Diagram.

5.1.1 Application Entity

An Application Entity is depicted as a box in an Application Data Flow Diagram, shown in Figure 5.1-1

Figure 5.1-1. Application Entity Convention

5.1.2 Real-World Activity

A Real-World Activity is depicted as a circle in an Application Data Flow Diagram, shown in Figure 5.1-2.

Figure 5.1-2. Real-World Activity Convention

Circles representing multiple Real-World Activities may overlap, indicating a degree of overlap in the Real-World Activities.

5.1.3 Local Relationships

A relationship between a local Real-World Activity and an Application Entity is depicted within an Application Data Flow Diagram by placing the local Real-World Activity to the left of the related Application Entity with a dashed line between them as shown in Figure 5.1-3.

Figure 5.1-3. Local Relationship Convention

An Application Entity may be associated with multiple Real-World Activities.

A Real-World Activity may be associated with multiple Application Entities.

5.1.4 Network-Associations

An Association between a local Application Entity and a remote Application Entity over a network supporting a remote Real-World Activity is depicted within an Application Data Flow Diagram by placing the remote Real-World Activity to the right of the related local Application Entity with one or two arrows drawn between them as shown in Figure 5.1-4. The dashed line represents the DICOM Standard Interface, which could be DICOM DIMSE, DICOM Web Services or DICOM Real-Time Video, between the local Application Entities, and whichever remote Application Entities handle the remote Real-World Activities. An arrow from the remote Real-World Activity to the local Application Entity indicates that the local Application Entity expects to receive an Association request when the remote Real-World Activity occurs, causing the local Application Entity to perform the local Real-World Activity.

Figure 5.1-4. Associations Convention

5.1.5 Media Storage File-Set Access

Application Entities exchanging information on media use the DICOM File Service as specified in PS3.10 for access to, or creation of, File-sets. This File Service provides operations that support three basic roles, which are File-set Creator (FSC), File-set Reader (FSR), and File-set Updater (FSU).

These roles are depicted on an Application Data Flow diagram by directional arrows placed between the local Application Entities and the DICOM Storage Media on which the roles are applied.

File-set Creator (FSC), denoted by
File-set Reader (FSR), denoted by
File-set Updater (FSU), denoted by
Physical movement of the medium, denoted by (with or without arrowhead)

Figure 5.1-5 illustrates the three basic roles.

Figure 5.1-5. File-Set Access

The local interactions shown on the left between a local Real-World activity and a local Application Entity are depicted by a dashed line. The arrows on the right represent access by the local Application Entity to a File-set on the DICOM Storage Medium. When an Application Entity supports several roles, this combination is depicted with multiple arrows corresponding to each of the roles. The dotted arrow symbolizes the removable nature of media for an interchange application.

Note

The use of two arrows relative to an FSC and an FSR should be distinguished from the case where a double arrow relative to an FSU is used. For example, an FSU may update a File-set without creating a new File-set, whereas a combined FSC and FSR may be used to create and verify a File-set.

6 Purpose of a Conformance Statement

An implementation need not employ all the optional components of the DICOM Standard. After meeting the minimum general requirements, a conformant DICOM implementation may utilize whatever SOP Classes, communications protocols, Media Storage Application Profiles, optional (Type 3) Attributes, codes and controlled terminology, etc., needed to accomplish its designed task.

Note

In fact, it is expected that an implementation might only support the SOP Classes related to its Real World Activities. For example, a simple film digitizer may not support the SOP Classes for other imaging modalities since such support may not be required. On the other hand, a complex storage server might be required to support SOP Classes from multiple modalities in order to adequately function as a storage server. The choice of which components of the DICOM Standard are utilized by an implementation depends heavily on the intended application and is beyond the scope of this Standard.

In addition, the DICOM Standard allows an implementation to extend or specialize the DICOM defined SOP Classes, as well as define Private SOP Classes.

A Conformance Statement allows a user to determine which optional components of the DICOM Standard are supported by a particular implementation, and what additional extensions or specializations an implementation adds. By comparing the Conformance Statements from two different implementations, a knowledgeable user should be able to determine whether and to what extent communications might be supported between the two implementations.

The content of Conformance Statement uses a consistent structure regardless of whether the implementation supports a DIMSE interface, a DICOM Media Storage interface, a DICOM Web Service interface, DICOM Real-Time Video interface, or a combination thereof. A single Conformance Statement shall be provided with the appropriate sections filled in. Sections not relevant for the implementation shall be kept and marked as not applicable. Subsections of a section marked as not applicable need not be included in the Conformance Statement (see the template in Annex N).

Note

A Conformance Statement is permitted to either consist of a single document file, or to be a main document file that references a number of annexes contained in one or more separate document files.

The first part of the Conformance Statement contains a DICOM Conformance Statement Overview, which is typically a short summary at the beginning of the document providing a high level description of the system. It should list the transfer capabilities, DIMSE Services, Media Services, DICOM Web Services and DICOM Real-Time Video Services, including their roles (SCU/SCP, FSC, FSR, etc.), and supported Transfer Syntaxes. This overview should also include a list of all Root Templates supported by the system.

6.1 Overview of Implementation Model Section For Conformance Statements

A functional overview containing the Application Data Flow Diagram that shows all the Application Entities. It also shows how they relate to both local and remote Real-World Activities.

6.2 Overview of Service and Interoperability Description Section For Conformance Statements

The Service and Interoperability description section of a Conformance Statement consists of the following major parts:

6.2.1 Mapping of Services to Application Entities

Provides an overview of the Application Entities and the Services supported by each AE.

6.2.2 Supported DIMSE Services

Provides a more detailed specification of each SOP Classes supported within the various services (Worklist, MPPS, Storage, Query/Retrieve, Print, etc.)
Provides for each SOP Class related to an Abstract Syntax, a list of any SOP options supported;
Provides a description of any extensions, specializations, and publicly disclosed privatizations in this implementation;
Provides a description of any implementation details that may be related to DICOM conformance or interoperability;
Provides a description of which codes and controlled terminology mechanisms are used.

6.2.3 Supported DICOM Web Services

Provides a more detailed specification of each DICOM Web Service supported

6.2.4 Supported Media Storage Services Section For Conformance Statements

The media storage section of a Conformance Statement consists of the following major parts:

a more detailed specification of each Application Entity listing the Media Storage Application Profiles supported, which outlines the policies with which it creates, reads, or updates File-sets on the media;
a description of any extensions, specializations, and publicly disclosed privatizations in this implementation such as Augmented or Private Application Profiles;
a description of any implementation details that may be related to DICOM conformance or interoperability;
a description of which codes and controlled terminology mechanisms are used.

6.3 Overview of DICOM Configuration Section For Conformance Statements

Section describing DICOM-related configuration details for the supported communication mechanisms:

DIMSE Services
DICOM Web Services
Media Storage Services
Real-Time Video Services
Audit Trail - Syslog

6.4 Overview of Network and Media Communication Details Section For Conformance Statements

The network and Media Communication Details section of a Conformance Statement consists of the following major parts:

Real-World activity Data Flow Diagrams that shows the sequencing activities among the Application Entities
Association parameters
Policies with which each Application Entity and Real-World Activity combination initiates or accepts Associations
Transfer syntaxes selection preferences
Status Codes and handling for DIMSE Services and DICOM Web Services

7 Conformance Requirements

An implementation claiming DICOM conformance may choose to support one or more of the following communication mechanisms:

Conformance to the DIMSE protocol (see Section 7.1.1 DIMSE Protocol Conformance Requirements)
Conformance to DICOM Web Services (see Section 7.1.2 DICOM Web Services Conformance Requirements)
Conformance to DICOM Media Storage (see Section 7.2 DICOM Media Interchange Conformance Requirements)
Conformance to the DICOM Real-Time Video (see Section 7.8 DICOM Real-Time Video Conformance Requirements)

7.1 DICOM Networking Conformance Requirements

7.1.1 DIMSE Protocol Conformance Requirements

An implementation claiming DIMSE network conformance shall:

conform to the minimum conformance requirements defined in this Section;
provide a Conformance Statement structured according to the rules and policies in this Part and follow the template provided in Annex N;
conform to at least one Standard or Standard Extended SOP Class as defined in PS3.4;

Note

Conformance to a Standard or Standard Extended SOP Class implies conformance to the related IOD outlined in PS3.3, the Data Elements defined in PS3.6, and the operations and notifications defined in PS3.7.

comply with the rules governing SOP Class types outlined in Section 7.3;
accept a Presentation Context for the Verification SOP Class as an SCP if the implementation accepts any DICOM Association requests;
produce and/or process Data Sets as defined in PS3.5;

Note

Conformance to PS3.5 also implies conformance to PS3.6.

obtain a legitimate right to a registered <org id> for creating UIDs (see PS3.5) if an implementation utilizes Privately Defined UIDs (i.e., UIDs not defined in the DICOM Standard);
support the following communication mode:
- TCP/IP (See PS3.8).

7.1.2 DICOM Web Services Conformance Requirements

An implementation claiming DICOM Web Services conformance shall:

conform to the minimum conformance requirements defined in this Section;
provide a Conformance Statement structured according to the rules and policies in this Part and follow the template provided in Annex N;
conform to at least one Service as defined in PS3.18;

Note

Conformance to a Service implies conformance to the related Resources defined in PS3.18 and IODs outlined in PS3.3, and Data Elements defined in PS3.6.
comply with the rules governing SOP Class types outlined in Section 7.3;
produce and/or process Data Sets as defined in PS3.5 and/or PS3.18;

Note

Conformance to PS3.5 and/or PS3.18 also implies conformance to PS3.6.
obtain a legitimate right to a registered <org id> for creating UIDs (see PS3.5) if an implementation utilizes Privately Defined UIDs (i.e., UIDs not defined in the DICOM Standard).

7.2 DICOM Media Interchange Conformance Requirements

An implementation claiming DICOM Media Interchange conformance shall:

conform to the minimum conformance requirements defined in this Section;
provide a Conformance Statement structured according to the rules and policies in this Part and follow the template provided in Annex N;
conform to at least one Standard Application Profile as defined in PS3.11;
support one of the Physical Media and associated Media Format, as specified by PS3.12;
comply with the rules governing SOP Class types outlined in Section 7.3;
comply with the specific rules governing media storage Application Profile according to their types as specified in Section 7.4. No other types of Application Profiles may be used;
read as an FSR or FSU all SOP Classes defined as mandatory by each of the supported Application Profiles encoded in any of the mandatory Transfer Syntaxes.
write as an FSC or FSU all SOP Classes defined as mandatory by each of the supported Application Profiles in one of the mandatory Transfer Syntaxes;
be able to gracefully ignore any Standard, Standard Extended, Specialized or Private SOP Classes that may be present on the Storage Medium but are not defined in any of the Application Profiles to which conformance is claimed.

Note

There may be more than one Application Profile used to create or read a File-set on a single physical medium (e.g., a medium may have a File-set created with Standard and Augmented Application Profiles).

be able to gracefully ignore Directory Records in the DICOMDIR file that do not correspond to Directory Records defined in any of the Application Profiles to which conformance is claimed.
access the File-set(s) on media using the standard roles defined in PS3.10;
produce and/or process Data Sets as defined in PS3.5 encapsulated in DICOM Files;

Note

Conformance to PS3.5 also implies conformance to PS3.6

obtain legitimate right to a registered <org id> for creating UIDs (see PS3.5) if an implementation utilizes Privately Defined UIDs (i.e., UIDs not defined in the DICOM Standard).

An implementation that does not meet all the above requirements shall not claim conformance to DICOM for Media Storage Interchange.

7.3 Rules Governing Types of SOP Classes

Each SOP Class published in a Conformance Statement is one of four basic types. Each SOP Class in an implementation claiming conformance to the DICOM Standard shall be handled in accordance with the following rules, as dictated by the type of SOP Class.

Standard SOP Classes conform to all relevant Parts of the DICOM Standard with no additions or changes.

To claim conformance to a Standard SOP Class, an implementation shall make a declaration of this fact in its Conformance Statement, and identify its selected options, roles, and behavior.

Standard Extended SOP Classes shall:

be a proper super set of one Standard SOP Class;
not change the semantics of any Standard Attribute of that Standard SOP Class;
not contain any Private Type 1, 1C, 2, or 2C Attributes, nor add additional Standard Type 1, 1C, 2 or 2C Attributes;
not change any Standard Type 3 Attributes to Type 1, 1C, 2, or 2C;
use the same UID as the Standard SOP Class on which it is based.

A Standard Extended SOP Class may include Standard and/or Private Type 3 Attributes beyond those defined in the IOD on which it is based as long as the Conformance Statement identifies the added Attributes and defines their relationship with the PS3.3 information model. If additional Type 3 Attributes drawn from the Data Dictionary in PS3.6 are sent that affect the encoding of other Attributes, or whose encoding depends on the values of other Attributes, their presence and use shall be consistent.

Note

E.g., An Attribute such as Pixel Padding Value (0028,0120) with a dictionary VR of US or SS would not be allowed to be present without Pixel Representation (0028,0103) also being present to resolve the encoding ambiguity. Further, Pixel Padding Value would not be allowed to be present in the absence of the Pixel Data (7FE0,0010) to which it applies.

An implementation claiming conformance with a Standard Extended SOP Class shall identify in its Conformance Statement the Standard SOP Class being extended, the options, roles, and behavior selected, and describe the Attributes being added with the Standard SOP Class's IOD Model and Modules.

Specialized SOP Classes shall:

be completely conformant to relevant Parts of the DICOM Standard;
be based on a Standard SOP Class, i.e.:
- contain all the Type 1, 1C, 2, and 2C Attributes of Standard SOP Class on which it is based;
- not change the semantics of any Standard Attribute;
- use a Privately Defined UID for its SOP Class (i.e., shall not be identified with a DICOM Defined UID);
be based on the DICOM Information Model in PS3.3 and PS3.4.

Specialized SOP Classes may:

contain additional Standard and/or Private Type 1, 1C, 2, or 2C Attributes;
add Private and Standard Type 3 Attributes, which may or may not be published in the Conformance Statement.

Note

The usage of any unpublished Attributes may be ignored by other users and providers of the Specialized SOP Class.
enumerate the permitted values for Attributes within the set allowed by the Standard SOP Class;
enumerate the permitted Templates for Content Items within the set allowed by the Standard SOP Class.

An implementation claiming conformance with a Specialized SOP Class shall include in its Conformance Statement the identity of the Standard SOP Class being specialized, a description of usage of all Standard and Private Type 1, 1C, 2, and 2C Attributes in the Specialized SOP Class, a description of the constraints on Attributes values and Templates, and the associated Privately Defined UID.

Private SOP Classes shall:

be completely conformant to relevant Parts of the DICOM Standard with the possible exception that support of the DICOM Default Transfer Syntax or a Transfer Syntax mandated by a media storage Application Profile is not required;
not change the PS3.6 specification of any Standard Attributes;
use a Privately Defined UID for its SOP Class (i.e., shall not be identified with a DICOM Defined UID);
not change existing DIMSE Services or create new ones;
not change existing DICOM File Services defined in PS3.10 or extend them in a manner that jeopardizes interoperability.

Private SOP Classes may:

use or apply DIMSE Services to privately defined or altered IODs (i.e., not necessarily be based on a Standard SOP Class);
use or apply Media Storage Operations to privately defined or altered IODs (i.e., not necessarily be based on a Standard SOP Class);
designate any Standard Attribute as Type 1, 1C, 2, or 2C regardless of the Type of the Attribute in other IODs;
define Private Attributes as Type 1, 1C, 2, or 2C;
include Private and Standard Type 3 Attributes, which may or may not be published in the Conformance Statement.

An implementation claiming conformance with a Private SOP Class shall provide a PS3.3, PS3.4, and PS3.6-like description of the Private SOP Class in the implementation's Conformance Statement, including descriptions of the usage of all Standard and Private Type 1, 1C, 2, or 2C Attributes in the SOP Class, the DICOM Information Model, and the Privately Defined UIDs.

Note

Unpublished SOP Classes (i.e., SOP Classes that are not defined in the DICOM Standard and are not defined in the Conformance Statement) are permitted in order to allow an implementation to support other abstract syntaxes within the DICOM Application Context. Such unpublished SOP Classes would utilize Privately Defined UIDs. The presence of an unpublished SOP Class does not prevent the implementation from being DICOM conformant but would have no meaning to other implementations and may be ignored.

7.4 Rules Governing Types of Application Profiles

Application Profile used in a Conformance Statement shall be of one of three basic types. Each Application Profile in an implementation claiming conformance to the DICOM Standard shall be handled in accordance with the following rules, as dictated by the type of Application Profile.

7.4.1 Standard Application Profile

A Standard Application Profile shall:

conform to all relevant Parts of DICOM with no changes;
support only one of the Physical Media and associated Media Format, as specified by PS3.12.

To claim conformance to a Standard Application Profile, an implementation shall make a declaration of this fact in its Conformance Statement, and identify its selected options, roles, and behavior.

An implementation of a Standard Application Profile may extend Standard SOP Classes of this Standard application profile. Such Standard Extended SOP Classes shall meet the requirements specified in Section 7.3.

7.4.2 Augmented Application Profile

An Augmented Application Profile shall:

be a proper super set of the Standard Application Profile. It adds the support of additional Standard or Standard Extended SOP Classes;
use the same Physical Media and its associated Media Format specified in the corresponding Standard Application Profile;
not include Specialized or Private SOP Classes.

An Augmented Application Profile may:

include one or more Standard or Standard Extended SOP Classes in addition to those of the corresponding Standard Application Profile. These additional SOP Classes may be mandatory or optional;
include the extensions (e.g., additional required keys, additional directory records) to the Basic Directory Information Object corresponding to the SOP Classes defined in a);
add one or more new roles (FSC, FSR, FSU).

To claim conformance to an Augmented Application Profile, an implementation shall make a declaration of this fact in its Conformance Statement, and shall identify the Standard Application Profile from which it is derived and specify the augmentations. The implementation shall also identify its selected options, roles, and behavior.

An implementation of a Augmented Application Profile may:

extend Standard SOP Classes of the corresponding Standard application profile. Such Standard Extended SOP Classes shall meet the requirements specified in Section 7.3;
also claim conformance to the Standard Application Profile on which this Augmented Profile is based. In this case, FSC and FSU implementations shall be able to restrict their behavior to the Standard Application Profile (i.e., provide a means to write only the Standard or Standard Extended SOP Classes defined in the corresponding Standard Application Profile).

7.4.3 Private Application Profile

A Private Application Profile:

conforms to PS3.10 and to the Media Storage Service Class specified in PS3.4;
support only one of the Physical Media and associated Media Format, as specified by PS3.12;

Note

The intent of these two conditions is to ensure that at least the DICOMDIR is readable by other APs.
complies with the rules governing SOP Classes in Section 7.3.

To claim conformance to a Private Application Profile, an implementation shall make a declaration of this fact in its Conformance Statement, and shall provide a description of the Application Profile patterned after the descriptions in PS3.11. The implementation shall also identify its selected options, roles, and behavior.

Note

An implementation that does not meet the provisions of Section 7, including the types of Application Profile, is not conformant to DICOM and so is outside the scope of DICOM conformance. Such an implementation is not an Application Profile in DICOM terminology. For example, if an implementation chooses to write DICOM files onto media that is not in PS3.12, or use a file system not defined for a specific media type in PS3.12, then that implementation cannot claim that it conforms to the DICOM Standard using that media or file system.

7.5 Conformance of DICOM Media

DICOM does not define conformance of a piece of medium in a generic sense. DICOM conformance of a piece of medium can only be evaluated within the scope of one or more media storage Application Profiles that define specific contexts for interoperability.

Note

One may accept the statement "this is a DICOM CD-R" when pointing to a storage medium. However, one should not state "this CD-R is DICOM conformant", but rather "this CD-R conforms to the Basic Cardiac X-ray Angiographic DICOM Application Profile".

7.6 Security Profiles

DICOM specifies methods for providing security at different levels of the ISO OSI Basic Reference Model through the use of mechanisms specific to a particular layer. The methods for applying these mechanisms are described in the various parts of the DICOM Standard. Some mechanisms and algorithms are specified in PS3.15 as Security Profiles. An implementation's Conformance Statement describes which Security Profiles can be used by that application.

Note

For example, the Basic TLS Secure Transport Connection Profile defines a mechanism for authenticating entities participating in the exchange of data, and for protecting the integrity and confidentiality of information during interchange.

An implementation shall list in its Conformance Statement any Security Profiles that it supports, how it selects which Security Profiles it uses, how it uses features of that Security Profile, and any extensions it makes to that Security Profile.

An implementation shall list in its Conformance Statement any additional use of the User Identity Association negotiation sub-item that is not specified in a standard Security Profile.

7.7 Transformation of DICOM SR to CDA

DICOM specifies the transformation of DICOM SR objects to CDA documents in PS3.20.

This transformation is unidirectional (DICOM SR to HL7 CDA). Conformance statements shall at a minimum state conformance to the top level templates used for the SR document and the CDA document.

7.8 DICOM Real-Time Video Conformance Requirements

An implementation claiming DICOM Real-Time Video conformance shall:

conform to the minimum conformance requirements defined in this Section;
provide a Conformance Statement structured according to the rules and policies in this Part and follow the template provided in Annex N;
conform to at least one Service as defined PS3.22;

Note

Conformance to a Service implies conformance to the related IODs outlined in PS3.3, and Data Elements defined in PS3.6.
comply with the rules governing SOP Class types outlined in Section 7.3;
produce and/or process Data Sets as defined in PS3.5 and/or PS3.22;

Note

Conformance to PS3.5 and/or PS3.22 also implies conformance to PS3.6;
obtain a legitimate right to a registered <org id> for creating UIDs (see PS3.5) if an implementation utilizes Privately Defined UIDs (i.e., UIDs not defined in the DICOM Standard).

A DICOM Conformance Statement Template (Retired)

Retired. See PS3.2-2022d

B Conformance Statement Sample Integrated Modality (Retired)

Retired. See PS3.2-2022d

C Conformance Statement Sample DICOMRis Interface (Retired)

Retired. See PS3.2-2022d

D Conformance Statement Sample DICOM Image Viewer (Retired)

Retired. See PS3.2-2022d

E Conformance Statement Example Print Server (Retired)

Retired. See PS3.2-2022d

F DICOM Conformance Statement Query-Retrieve-Server (Retired)

Retired. See PS3.2-2022d

G Conformance Statement Sample ImageViewer with Hanging Protocol Support (Retired)

Retired. See PS3.2-2022d

H DICOM Conformance Statement Medication-System-Gateway (Retired)

Retired. See PS3.2-2022d

I Conformance Statement Sample WADO Service (Retired)

Retired. See PS3.2-2022d

J Conformance Statement Sample STOW Service (Retired)

Retired. See PS3.2-2022d

K Conformance Statement Sample QIDO-RS Provider (Retired)

Retired. See PS3.2-2022d

L Conformance Statement Sample DICOM-RTV Service Provider (Retired)

Retired. See PS3.2-2022d

M Conformance Statement Sample DICOM-RTV Service Consumer (Retired)

Retired. See PS3.2-2022d

N DICOM Conformance Statement Template (Normative)

This Annex provides a template for a DICOM Conformance Statement. For convenience a Microsoft Word version of this template can be found at: http://www.dicomstandard.org/resources/templates

Note

This Annex defines the normative content of a DICOM Conformance Statement. Changes to this Annex may not be immediately reflected in the Microsoft Word version of this template. When the current release of DICOM PS3.2 and the Microsoft Word version of this template do not match, it is the responsibility of the editor of a DICOM Conformance Statement to ensure the correct current content is reflected in the created DICOM Conformance Statement.

The content and organization of DICOM Conformance Statements shall conform to this template.

The following formatting conventions are used in this template to guide Conformance Statement authors. Based on the format of the text used in the template, a DICOM Conformance Statement shall:

Include, without modification, text shown in regular font style (i.e., non-italic). Such text is standard "boilerplate" like introductions to sections, tables that list mandatory Attributes, etc.
Remove text shown in italic font style and [enclosed by square brackets]. Such text provides instructions to Conformance Statement authors on how to use this template. The text may be retained until the author has no further use for it but should be removed before publication of the Conformance Statement.
Either remove text shown in italic font style or modify it appropriately and change it to regular font style. Such text is example text that may provide typical phrasing, examples of the types of topics that might be addressed in a certain section, or list optional Attributes which should be deleted if not supported, etc.
Replace text <enclosed in angle brackets> with appropriate text. Such text is a placeholder for variables like the product name. Remove the < > characters when replacing the text.
Replace text <<enclosed in double angle brackets>> with a single Value from the enclosed list. Such text provides a list of alternatives such as DICOM Defined Terms for an Attribute Value. Remove the << >> characters when replacing the text.
- If Values other than those listed may be used, that is indicated by an ellipsis before the closing angle brackets (i.e., "…>>")
- If multiple Values can be selected, instruction text will document that fact.
- If some of the multiple Values are mandatory, the mandatory Values are shown in regular font style and the optional Values are shown in italic font style.

Note

Some sections and tables mix text in multiple fonts. Each piece of text is treated accordingly to its font style.

The following conventions are used in this template to encourage uniformity that makes it easier for consumers to read Conformance Statements from different vendors and find specific pieces of information. A DICOM Conformance Statement shall:

Indicate support in tables (e.g., in the "SCU" and "SCP" column of table with rows for SOP Classes) by using "Y" for yes and "N" for no.
Include rows in tables only for things (e.g., SOP Classes, Services, Attributes, etc.) supported by your implementation. Do not include rows for things that are not supported.
Format supported Value ranges in table cells using square brackets as follows: [lower Value … upper Value].
Format multiple supported Values in table cells separated by a semicolon in the cell.
Replace the content of Sections that are not applicable to the implementation with the text "N/A" and append "- N/A" to the end of the section title. This is done rather than deleting the section; however, if all the subsections in a section are marked "N/A", the subsections may be deleted, and, if so, the parent section should have the text "N/A" as content, and its title should have "- N/A" appended to its original title. This keeps the numbering of sections consistent throughout DICOM Conformance Statements for easier comparison.
If Sections need to be added, append them at the end of the parent Section in order to keep Section numbering consistent with this template.
Tables shall be numbered sequentially within each major subsection. It is not necessary to follow the table numbering in the template, if specific tables are not applicable for the product described in this DICOM Conformance Statement.
Consider providing information (e.g., extensive explanation) as a footnote under the table when the information exceeds the comfortable size of the cell.

The Annexes are mandatory parts of this template and shall be populated if applicable to the implementation. For example, the IOD definitions must be filled in if the implementation supports creation of DICOM SOP Instances.

If throughout the document any of the tables get too wide for portrait mode it is recommended to switch to landscape mode for the table.

Tables are split into subsections for better readability. If a subsection of the table is not supported, remove the complete subsection from the table.

If the DICOM Conformance Statement describes multiple products/versions in one document, the cover page should indicate which products/versions are covered.

Ensure spelling throughout the entire DICOM Conformance Statement is consistent with the DICOM Standard.

If this template contradicts normative statements in other Parts of the DICOM Standard, those other Parts take precedence.

The template content begins after this line.

[When using this template for creation of a DICOM Conformance Statement, start numbering the actual document content with Section 1 for the Overview, not with N.1.]

N.0 Cover Page

[A DICOM Conformance Statement shall have a cover page, which shall include:

The commercial name(s) and version(s) of the concerned product or products (if applicable to several products) including all optional features. The product version shall correspond to the functionality as described in this Conformance Statement.
Date of the document

]

N.1 Overview

[Provide a short description of the product's DICOM functionality.]

[Edit the following illustration, depicting DICOM Services implemented in your product and the interactions with remote systems connected to product. Replace <Product> with your product name and <Remote Systems x> with a system category such as modality, PACS, RIS, or <DICOM Service> by the applicable service such as storage, query/ retrieve, query modality worklist, ….]

Figure N.1-1. Overview of Implemented Services

N.1.1 Content and Transfer

Table N.1-1 lists all Storage SOP Classes and the supported transfer mechanisms as well as the usage scenarios for those instances.

The "Transfer Syntax Set" column lists the sets of Transfer Syntaxes defined in Table N.1-2 that are applicable to each SOP Class. The "DIMSE", "DICOM Web" and "Media Services" columns indicate the roles supported for each SOP Class.

The "Function" columns indicate how the instances are used by the system:

Create: The system creates instances of the SOP Class. The type of the created SOP Class is indicated by one of the following abbreviations:
- S: Standard SOP Class
- SE: Standard Extended SOP Class
- SP: Specialized SOP Class
- P: Private SOP Class
Display: The system displays the instances of the SOP Class to the user, either by displaying the SOP Instances natively or by applying instances of another suitable SOP Class to the image instances (e.g., a Presentation State or CAD SR).
Process: The system processes the instances of the SOP Class to derive some further information that is made available to the user (e.g., a CAD processing algorithm, or a 3D Rendering).
Archive: The system stores the instances of the SOP Class and makes them available again.

[List all Storage SOP Classes supported by the system in numerical order of the SOP Class UID. Indicate in the "Transfer Syntax Set" column which of the Transfer Syntax Sets defined in Table N.1-2 are supported. Note that for each SOP Class, multiple Transfer Syntax Sets can be supported.]

[For the "Create Function" columns, use Values as defined above. For all other supported role/"Function" columns, list "Y" for yes and "N" for no.]

Table N.1-1. Storage SOP Classes

SOP Classes		Transfer Syntax Set	DIMSE Services		DICOM Web Services		Media Services			Function
			SCU	SCP	UA	OS	FSC	FSU	FSR	Create	Display	Process	Archive
Media Storage Directory Storage	1.2.840.10008.1.3.10	NI
Computed Radiography Image Storage	1.2.840.10008.5.1.4.1.1.1	U; LL; L
Digital X-Ray Image Storage - For Presentation	1.2.840.10008.5.1.4.1.1.1.1	U; LL; L
Digital X-Ray Image Storage - For Processing	1.2.840.10008.5.1.4.1.1.1.1.1	U; LL; L
Digital Mammography X-Ray Image Storage - For Presentation	1.2.840.10008.5.1.4.1.1.1.2	U; LL
VL Photographic Image Storage	1.2.840.10008.5.1.4.1.1.77.1.4	U; LL; L
Video Photographic Image Storage	1.2.840.10008.5.1.4.1.1.77.1.4.1	V
Comprehensive SR Storage	1.2.840.10008.5.1.4.1.1.88.33	NI								See Table N.1-3
Mammography CAD SR Storage	1.2.840.10008.5.1.4.1.1.88.50									See Table N.1-3

[Table N.1-2 defines some example Transfer Syntax Sets that are referenced by their abbreviation in Table N.1-1 above. You can modify the Transfer Syntax Sets to match your product implementation and extend the Table with additional Transfer Syntax Sets as needed. For additional Transfer Syntax Sets, create additional rows and assign abbreviations in "() " that can be referenced in the Table above.]

Table N.1-2. Supported Transfer Syntaxes

Transfer Syntax Set	Transfer Syntax Name	Transfer Syntax UID	DICOM Web Service Bulkdata Media Type
Lossless Compressed Transfer Syntax Set (LL)	JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14 [Selection Value 1])	1.2.840.10008.1.2.4.70	image/jpeg
	JPEG 2000 Image Compression (Lossless Only)	1.2.840.10008.1.2.4.90	image/jp2
	RLE Lossless	1.2.840.10008.1.2.5	image/x-dicom-rle
Lossy Compressed Transfer Syntax Set (L)	JPEG Baseline (Process 1)	1.2.840.10008.1.2.4.50	image/jpeg
	JPEG Extended (Process 2 & 4)	1.2.840.10008.1.2.4.51	image/jpeg
	JPEG 2000 Image Compression	1.2.840.10008.1.2.4.91	image/jp2
Non-Image Transfer Syntax Set (NI)	Implicit VR Little Endian	1.2.840.10008.1.2	N/A
	Explicit VR Little Endian	1.2.840.10008.1.2.1	application/octet-stream
	Explicit VR Big Endian (Retired)	1.2.840.10008.1.2.2	N/A
Uncompressed Transfer Syntax Set (U)	Implicit VR Little Endian	1.2.840.10008.1.2	N/A
	Explicit VR Little Endian	1.2.840.10008.1.2.1	application/octet-stream
	Explicit VR Big Endian (Retired)	1.2.840.10008.1.2.2	N/A
Video Transfer Syntax Set (V)	MPEG2 Main Profile / Main Level	1.2.840.10008.1.2.4.100	video/mpeg2
	MPEG2 Main Profile / High Level	1.2.840.10008.1.2.4.101	video/mpeg2
	MPEG-4 AVC/H.264 High Profile / Level 4.1	1.2.840.10008.1.2.4.102	video/mp4
	MPEG-4 AVC/H.264 BD-compatible High Profile / Level 4.1	1.2.840.10008.1.2.4.103	video/mp4
	MPEG-4 AVC/H.264 High Profile / Level 4.2 For 2D Video	1.2.840.10008.1.2.4.104	video/mp4
Real-Time Video Transfer Syntax Set (RTV)	SMPTE ST 2110-20 Uncompressed Progressive Active Video	1.2.840.10008.1.2.7.1	N/A
	SMPTE ST 2110-20 Uncompressed Interlaced Active Video	1.2.840.10008.1.2.7.2	N/A
	SMPTE ST 2110-30 PCM Digital Audio	1.2.840.10008.1.2.7.3	N/A

N.1.1.1 Structured Reporting Root Template IDs

Table N.1-3 lists all Template IDs (TID) of Root Templates that are supported by the system. The "Function" column indicates how the system uses the content of the DICOM SR:

CREATE: The system creates instances using the specified TID.
RENDER: The system displays the content of the SR, without using the data for any processing.
EXTRACT_DATA: The system can extract structured data from the content and use the data for subsequent processing (e.g., reporting).
OVERLAY: The system uses the information in the SR to display information directly on the images (e.g., Mammography CAD markers).
ARCHIVE: The system stores instances for later retrieval.

The "SOP Class UID" column indicates which of the SR Storage SOP Classes are used to encode the information or to store it. If multiple SOP Classes are supported the "Condition" column describes the conditions for using the different SOP Classes.

[Table N.1-3 provides some examples, add/remove TIDs to match your product implementation. Add Root TIDs in ascending numerical order.

For guidance on the meaning of the columns see description above. Note that in the "Function" column multiple Values can be listed.

It is recommended to add a link to the "Root Template ID" column to the relevant subsection of Section N.10.]

Table N.1-3. Supported Root SR Template IDs (TIDs)

Name	Root TID	Function	SOP Classes		Condition
Mammography CAD Document Root	4000	CREATE; ARCHIVE; OVERLAY	Comprehensive SR Storage	1.2.840.10008.5.1.4.1.1.88.33	Based on association negotiation
Mammography CAD Document Root	4000	CREATE; ARCHIVE; OVERLAY	Mammography CAD SR Storage	1.2.840.10008.5.1.4.1.1.88.50	Based on association negotiation
Adult Echocardiography Procedure Report	5200	EXTRACT_DATA	Comprehensive SR Storage	1.2.840.10008.5.1.4.1.1.88.33

N.1.2 DIMSE Services

N.1.2.1 Verification

Table N.1-4 lists support for the Verification SOP Class.

[Modify Table N.1-4 to reflect support for the Verification SOP Class.]

Table N.1-4. Verification SOP Class

SOP Classes		Transfer Syntax		SCU	SCP
Verification	1.2.840.10008.1.1	Implicit VR Little Endian	1.2.840.10008.1.2
Verification	1.2.840.10008.1.1	Explicit VR Little Endian	1.2.840.10008.1.2.1

N.1.2.2 Storage

For details on supported Storage SOP Classes see Section N.1.1.

N.1.2.3 Workflow Management

Table N.1-5 lists all supported Workflow Management SOP Classes.

[Modify Table N.1-5 to reflect SOP Classes in the Workflow Management area that are supported. For each supported service indicate the role it supports. If it neither supports a SOP Class as SCU nor SCP, remove the respective line from the Table]

Table N.1-5. Workflow Management SOP Classes

SOP Classes		Transfer Syntax
Modality Worklist Information Model - FIND	1.2.840.10008.5.1.4.31	Implicit VR Little Endian	1.2.840.10008.1.2
Modality Worklist Information Model - FIND	1.2.840.10008.5.1.4.31	Explicit VR Little Endian	1.2.840.10008.1.2.1
Modality Performed Procedure Step	1.2.840.10008.3.1.2.3.3	Implicit VR Little Endian	1.2.840.10008.1.2
Modality Performed Procedure Step	1.2.840.10008.3.1.2.3.3	Explicit VR Little Endian	1.2.840.10008.1.2.1
Storage Commitment Push Model	1.2.840.10008.1.20.1	Implicit VR Little Endian	1.2.840.10008.1.2
Storage Commitment Push Model	1.2.840.10008.1.20.1	Explicit VR Little Endian	1.2.840.10008.1.2.1
Unified Procedure Step - Push	1.2.840.10008.5.1.4.34.6.1	Implicit VR Little Endian	1.2.840.10008.1.2
Unified Procedure Step - Push	1.2.840.10008.5.1.4.34.6.1	Explicit VR Little Endian	1.2.840.10008.1.2.1
Unified Procedure Step - Watch	1.2.840.10008.5.1.4.34.6.2	Implicit VR Little Endian	1.2.840.10008.1.2
Unified Procedure Step - Watch	1.2.840.10008.5.1.4.34.6.2	Explicit VR Little Endian	1.2.840.10008.1.2.1
Unified Procedure Step - Pull	1.2.840.10008.5.1.4.34.6.3	Implicit VR Little Endian	1.2.840.10008.1.2
Unified Procedure Step - Pull	1.2.840.10008.5.1.4.34.6.3	Explicit VR Little Endian	1.2.840.10008.1.2.1
Unified Procedure Step - Event	1.2.840.10008.5.1.4.34.6.4	Implicit VR Little Endian	1.2.840.10008.1.2
Unified Procedure Step - Event	1.2.840.10008.5.1.4.34.6.4	Explicit VR Little Endian	1.2.840.10008.1.2.1
Instance Availability Notification	1.2.840.10008.5.1.4.33	Implicit VR Little Endian	1.2.840.10008.1.2
Instance Availability Notification	1.2.840.10008.5.1.4.33	Explicit VR Little Endian	1.2.840.10008.1.2.1

N.1.2.4 Query/Retrieve

Table N.1-6 lists all supported Query/Retrieve SOP Classes.

[Table N.1-6 lists some SOP Classes for querying and retrieving from a remote DICOM node, nevertheless PS3.4 defines many more additional SOP Classes for querying and retrieving. If your product supports any of these additional SOP Classes (e.g., any of the SOP Classes supporting C-GET), add them to Table N.1-6 and delete the SOP Classes not supported by your product. If you neither support a SOP Class as SCU or SCP, remove the respective line from Table N.1-6.]

Table N.1-6. Query/Retrieve SOP Classes

SOP Classes		Transfer Syntax
Patient Root Query/Retrieve Information Model - FIND	1.2.840.10008.5.1.4.1.2.1.1	Implicit VR Little Endian	1.2.840.10008.1.2
Patient Root Query/Retrieve Information Model - FIND	1.2.840.10008.5.1.4.1.2.1.1	Explicit VR Little Endian	1.2.840.10008.1.2.1
Study Root Query/Retrieve - Information Model - FIND	1.2.840.10008.5.1.4.1.2.2.1	Implicit VR Little Endian	1.2.840.10008.1.2
Study Root Query/Retrieve - Information Model - FIND	1.2.840.10008.5.1.4.1.2.2.1	Explicit VR Little Endian	1.2.840.10008.1.2.1
Patient Root Query/Retrieve - Information Model - MOVE	1.2.840.10008.5.1.4.1.2.1.2	Implicit VR Little Endian	1.2.840.10008.1.2
Patient Root Query/Retrieve - Information Model - MOVE	1.2.840.10008.5.1.4.1.2.1.2	Explicit VR Little Endian	1.2.840.10008.1.2.1
Study Root Query/Retrieve - Information Model - MOVE	1.2.840.10008.5.1.4.1.2.2.2	Implicit VR Little Endian	1.2.840.10008.1.2
Study Root Query/Retrieve - Information Model - MOVE	1.2.840.10008.5.1.4.1.2.2.2	Explicit VR Little Endian	1.2.840.10008.1.2.1

N.1.2.5 Printing

Table N.1-7 lists all supported Printing SOP Classes.

[Table N.1-7 lists some SOP Classes for Printing and PS3.4 defines additional SOP Classes for printing. If your product supports any of these additional SOP Classes, add them to Table N.1-7, and remove any rows that do not apply to your product. If you neither support a SOP Class as SCU nor SCP, remove the respective line from Table N.1-7.]

Table N.1-7. Printing SOP Classes

SOP Classes		Transfer Syntax
Basic Grayscale Print Management Meta	1.2.840.10008.5.1.1.9	Implicit VR Little Endian	1.2.840.10008.1.2
Basic Grayscale Print Management Meta	1.2.840.10008.5.1.1.9	Explicit VR Little Endian	1.2.840.10008.1.2.1
Basic Color Print Management Meta	1.2.840.10008.5.1.1.18	Implicit VR Little Endian	1.2.840.10008.1.2
Basic Color Print Management Meta	1.2.840.10008.5.1.1.18	Explicit VR Little Endian	1.2.840.10008.1.2.1
Basic Annotation Box	1.2.840.10008.5.1.1.15	Implicit VR Little Endian	1.2.840.10008.1.2
Basic Annotation Box	1.2.840.10008.5.1.1.15	Explicit VR Little Endian	1.2.840.10008.1.2.1
Print Job	1.2.840.10008.5.1.1.14	Implicit VR Little Endian	1.2.840.10008.1.2
Print Job	1.2.840.10008.5.1.1.14	Explicit VR Little Endian	1.2.840.10008.1.2.1
Presentation LUT	1.2.840.10008.5.1.1.23	Implicit VR Little Endian	1.2.840.10008.1.2
Presentation LUT	1.2.840.10008.5.1.1.23	Explicit VR Little Endian	1.2.840.10008.1.2.1
Printer Configuration Retrieval	1.2.840.10008.5.1.1.17.376	Implicit VR Little Endian	1.2.840.10008.1.2
Printer Configuration Retrieval	1.2.840.10008.5.1.1.17.376	Explicit VR Little Endian	1.2.840.10008.1.2.1

N.1.3 DICOM Web Services

N.1.3.1 URI Service (WADO-URI)

Table N.1-8 lists details on the support of the URI Service.

[Complete Table N.1-8 to indicate support for the URI Web Service.]

Table N.1-8. URI Service

Service	Transaction	User Agent	Origin Server
URI Web Service (WADO-URI)	Retrieve DICOM Instances
URI Web Service (WADO-URI)	Retrieve Rendered Instance

For resources supported see Table N.1-1 in Section N.1.1

N.1.3.2 Studies Service

Table N.1-9 lists details on the support of the Studies Service.

[Complete Table N.1-9 to indicate support for the Studies Web Service]

Table N.1-9. Study Service

Service	Transaction	Resource
Studies Web Service	Retrieve Capabilities
	Retrieve (WADO-RS)	Study
		Study Metadata
		Study Bulkdata
		Study Pixel Data
		Rendered Study
		Rendered MPR Volume Study
		Rendered 3D Volume Study
		Study Thumbnail
		Series
		Series Metadata
		Series Bulkdata
		Series Pixel Data
		Rendered Series
		Rendered MPR Volume Series
		Rendered 3D Volume Series
		Series Thumbnail
		Instance
		Instance Metadata
		Instance Bulkdata
		Instance Pixel Data
		Rendered Instance
		Rendered MPR Volume Instance
		Rendered 3D Volume Instance
		Instance Thumbnail
		Frames
		Rendered Frames
		Rendered MPR Volume Frames
		Rendered 3D Volume Frames
		Frame Thumbnail
		Bulkdata
	Search (QIDO-RS)	All Studies
		Study
		Study's Series
		Study's Instances
		All Series
		Series
		Series Instances
		All Instances
		Instance
	Store (STOW-RS)	All Studies
		Study
		Bulkdata

[If your Origin Server supports any Rendered MPR Volume Resources or Rendered 3D Volume Resources, indicate supported SOP Classes in the “Process” column of Table N.1-1.]

N.1.3.3 Worklist Service

Table N.1-10 lists details on the support of the Worklist Service.

[Complete Table N.1-10 to indicate support for the Worklist Web Service.]

Table N.1-10. Worklist Service

Service	Transaction	Resource
Worklist Web Service (UPS-RS)	Retrieve Capabilities
	Create Workitem	Worklist
	Create Workitem	Workitem
	Update Workitem	Workitem
	Retrieve Workitem	Workitem
	Change Workitem State	Workitem
	Request Cancellation	Workitem
	Search	Worklist
	Subscribe	Worklist
		Filtered Worklist
		Workitem
	Unsubscribe	Worklist
		Filtered Worklist
		Workitem
	Suspend Global Subscription	Worklist
	Suspend Global Subscription	Filtered Worklist
	Workitem Event Report

N.1.3.4 Non-Patient Instance Service

Table N.1-11 lists details on the support of Non-Patient Instances Service.

For details on the supported resource categories (e.g., Color Palette, Defined Procedure Protocol, Hanging Protocol or Implant Templates), see Table N.1-1.

[Complete Table N.1-11 to indicate support for the Non-Patient Instance Web Service.]

Table N.1-11. Non-Patient Instance Service

Service	Transaction	Resource	User Agent	Origin Server
Non-Patient Instances Web Service	Retrieve Capabilities
	Retrieve
	Store
	Search (Note)

N.1.3.5 Storage Commitment Service

Table N.1.3.5-1 lists details on the support of the Storage Commitment Service.

[Complete Table N.1.3.5-1 to indicate support for the Storage Commitment Web Service.]

Table N.1.3.5-1. Storage Commitment Service

Service	Transaction	Resource	User Agent	Origin Server
Storage Commitment Service	Request	commitment-requests
Storage Commitment Service	Result Check	commitment-requests

N.1.4 Media Services

Table N.1-12 lists all supported Media Application Profiles.

[Table N.1-12 lists Media Storage Application profiles and supported roles. Extend/modify the Table to list the profiles supported by your system.]

Table N.1-12. Supported Media Application Profiles

Media Storage Application Profile	FSC	FSR	FSU
Compact Disk - Recordable
STD-GEN-CD
AUG-GEN-CD

DVD
AUG-GEN-DVD-JPEG
AUG-GEN-DVD-J2K
STD-GEN-DVD-JPEG
STD-GEN-DVD-J2K

USB
AUG-GEN-USB-J2K
STD-GEN-USB-J2K

N.1.5 Real-Time Video Service

Table N.1-13 lists all supported Real-Time Video SOP Classes and Transfer Syntaxes.

[List all supported Real-Time Video SOP Classes in Table N.1-13. For the "Transfer Syntax Set" column use Transfer Syntax Sets defined in Table N.1-2.]

Table N.1-13. Supported Real-Time Video SOP Classes

SOP Classes		Transfer Syntax Set	RTV
SOP Classes		Transfer Syntax Set	SCU	SCP
Video Endoscopic Image Real-Time Communication	1.2.840.10008.10.1	RTV
Video Photographic Image Real-Time Communication	1.2.840.10008.10.2	RTV
Audio Waveform Real-Time Communication	1.2.840.10008.10.3	RTV
Rendition Selection Document Real-Time Communication	1.2.840.10008.10.4	N/A

N.1.6 De-identification Profiles

Table N.1-14 lists all supported de-identification profiles and options.

[Complete Table N.1-14 to list supported De-Identification profiles and options. If you do not support de-identification, remove this table, and mark section as N/A]

Table N.1-14. De-Identification Profiles

Profile	Option
Basic Application-Level Confidentiality Profile	Clean Pixel Data Option
Basic Application-Level Confidentiality Profile	Clean Structured Content Option

N.1.7 Specific Character Sets

[List all supported Character Sets and the IANA name as well as a description in Table N.1-15.]

Table N.1-15. Supported Specific Character Sets

Defined Term	IANA	Description
Single-Byte Character Sets without Code Extensions
ISO_IR 6	ISO-646 or US-ASCII	Default Repertoire
ISO_IR 100	ISO-8859-1	Latin Alphabet No.1 (West Europe)

Single-Byte Character Sets with Code Extension
ISO 2022 IR 6		Default Repertoire
ISO 2022 IR 100		Latin Alphabet No. 1 (West Europe)

Multi-Byte Character Sets without Code Extensions
ISO_IR 192	UTF-8	Unicode in UTF-8 Level 3
GB18030	GB18030	GB18030-2000 (P.R China Norm GB18030)

Multi-Byte Character Sets with Code Extensions
ISO 2022 IR 87	ISO-2022-JP	Japanese JIS X 0208
ISO 2022 IR 149	ISO-2022-KR	Korean

N.2 Table of Contents

[The Table of Contents shall be provided to assist readers in easily finding the needed information.]

N.3 Introduction

N.3.1 Revision History

[Provide the revision history for this document including the document revision, the document revision date, the product version(s) the DICOM Conformance Statement applies to and give a high-level description of changes.]

Revision	Date	Product Version(s)	Change
<Revision>	<Date>	<Product Version(s)>	<Change>

N.3.2 Audience

This document is intended for the audience listed below. It is assumed that the reader has a working knowledge of the DICOM Standard.

[Below is a list of typical users of a DICOM Conformance Statement, modify and add other user groups if needed.]

The document structure was designed for easier access to relevant information for different user groups:

Clinical Users, who want to get an overview of the implemented interoperability features of the system can see Section N.4 Implementation Model.
Personnel involved in Sales can use the information in Section N.1 to assess the compatibility between different systems involved in a sales situation.
System Integrators can use information in Section N.6 during system installation and also information from Section N.5 Service and Interoperability Description for details regarding the implemented services.
Field Service Engineers can use the details from Section N.5 Service and Interoperability Description and from Section N.7 Network and Media Communication Details for troubleshooting.
Hospital IT staff focusing on security can use the details provided in Section N.8 Security regarding implemented Security features.
Research Personnel may be interested in using information provided in Section N.9 Information Object Definitions (IODs) or Section N.10 Structured Report Content Encoding to get detailed imaging and measurement information.

N.3.3 Remarks

[Any important remarks, disclaimers, and general information are specified. The following example may be used as a template.]

The scope of this DICOM Conformance Statement is to facilitate integration between < Product> and other DICOM products. The Conformance Statement should be read and understood in conjunction with the DICOM Standard [1]. DICOM by itself does not guarantee interoperability.

The Conformance Statement does, however, facilitate a first-level comparison for interoperability between different applications supporting compatible DICOM functionality.
This Conformance Statement should not replace validation with other DICOM equipment to ensure proper exchange of intended information. In fact, it is the user's responsibility to perform the following validation activities:
- The comparison of Conformance Statements from <Product> and other DICOM conformant equipment is the first step towards assessing interconnectivity and interoperability between those systems.
- Test procedures should be defined and executed to validate the required level of interoperability with specific DICOM conformant equipment, as established by the healthcare facility.

[If the product has an IHE Integration Statement, the following statement may be applicable]:

<Product> has participated in an industry-wide testing program sponsored by Integrating the Healthcare Enterprise (IHE). The IHE Integration Statement of <Product> together with the IHE Technical Framework may facilitate the process of validation testing.

N.3.4 Terms and Definitions

[Terms and definitions should be listed here. The following list includes DICOM terms, delete terms that are not used throughout the Conformance Statement, but do not add or modify terms listed here.]

The following list includes DICOM Terms, that are used throughout this Conformance Statement:

Abstract Syntax	The information agreed to be exchanged between applications, generally equivalent to a Service/Object Pair (SOP) Class. Examples: Verification SOP Class, Modality Worklist Information Model Find SOP Class, Computed Radiography Image Storage SOP Class.
Application Entity (AE)	A representation of the external behavior of an application process in terms of DICOM Network Services, Web Services and/or media exchange capabilities implemented in one or more roles. A single device may have multiple Application Entities.
Application Entity Title (AET)	The externally known name of an Application Entity, used to identify a DICOM application to other DICOM applications on the network.
Application Context	The specification of the type of communication used between Application Entities. Example: DICOM network protocol.
Association	A network communication channel set up between Application Entities.
Attribute	A unit of information in an Information Object Definition; a Data Element identified by a tag. The information may be a complex data structure (Sequence), itself composed of lower-level data elements. Examples: Patient ID (0010,0020), Accession Number (0008,0050), Photometric Interpretation (0028,0004), Procedure Code Sequence (0008,1032).
Data Element	A unit of information as defined by a single entry in the data dictionary. An encoded Information Object Definition (IOD) Attribute that is composed of, at a minimum, three fields: a Data Element Tag, a Value Length, and a Value Field. For some specific Transfer Syntaxes, a Data Element also contains a VR Field where the Value Representation of that Data Element is specified explicitly
Information Object Definition (IOD)	The specified set of Attributes that comprise a type of data object; does not represent a specific instance of the data object, but rather a class of similar data objects that have the same properties. Examples: MR Image IOD, CT Image IOD, Print Job IOD. The Attributes within an IOD may be specified as Mandatory (Type 1), Required but possibly unknown (Type 2), or Optional (Type 3), and there may be conditions associated with the use of an Attribute (Types 1C and 2C).
Media Application Profile	The specification of DICOM information objects and encoding exchanged on removable media (e.g., CDs).
Module	A set of Attributes within an Information Object Definition that are logically related to each other. Example: Patient Module includes Patient's Name, Patient ID, Patient' Birth Date, and Patient's Sex.
Negotiation	First phase of Association establishment that allows Application Entities to agree on the types of data to be exchanged and how that data will be encoded.
Origin Server	Refers to the program that can originate authoritative responses to HTTP requests for a given Target Resource. The term "server" refers to any implementation that receives a web service request message from a user agent.
Presentation Context	The set of DICOM Network Services used over an Association, as negotiated between Application Entities; includes Abstract Syntaxes and Transfer Syntaxes.
Private SOP Class	A SOP Class that is not defined in the DICOM Standard but is published in an implementation's Conformance Statement.
Protocol Data Unit (PDU)	A packet (piece) of a DICOM message sent across the network. Devices must specify the maximum size packet they can receive for DICOM messages.
Security Profile	A set of mechanisms, such as encryption, user authentication, or digital signatures, used by an Application Entity to ensure confidentiality, integrity, and/or availability of exchanged DICOM data.
Service Class Provider (SCP)	Role of an Application Entity that provides a DICOM network service; typically, a server that performs operations requested by another Application Entity (Service Class User). Examples: Picture Archiving and Communication System (image storage SCP, and image query/retrieve SCP), Radiology Information System (modality worklist SCP).
Service Class User (SCU)	Role of an Application Entity that uses a DICOM Network Service; typically, a client. Examples: imaging modality (image storage SCU, and modality worklist SCU), imaging workstation (image query/retrieve SCU).
Service/Object Pair Class (SOP Class)	The specification of the network or media transfer (service) of a particular type of data (object) ; the fundamental unit of a DICOM interoperability specification. Examples: Ultrasound Image Storage Service, Basic Grayscale Print Management.
Service/Object Pair Instance (SOP Instance)	An information object; a specific occurrence of information exchanged in a SOP Class. E.g., a specific X-ray image.
Specialized SOP Class	A SOP Class that is derived from the Standard that is specialized by additional type 1, 1C, 2, 2C, or 3 Attributes, by enumeration of specific permitted Values for Attributes, or by enumeration of specific permitted Templates. The additional Attributes may either be drawn from the Data Dictionary in PS3.6 or may be Private Attributes.
Standard SOP Class	A SOP Class defined in the Standard, and that is implemented and used without any modifications.
Standard Extended SOP Class	A SOP Class that is defined in the standard, and that is extended by additional type 3 Attributes. The additional Attributes may either be drawn from the DICOM Data Dictionary in PS3.6 or may be Private Attributes.
Tag	A 32-bit identifier for a Data Element, represented as a pair of four-digit hexadecimal numbers, the "group" and the "element". If the "group" number is odd, the tag is for a private (manufacturer-specific) data element. Examples: (0010,0020) [Patient ID], (07FE,0010) [Pixel Data], (0019,0210) [private data element].
Transfer Syntax	The encoding used for exchange of DICOM information objects and messages. Examples: JPEG compressed (images), Little Endian Explicit Value Representation.
TLS-Secured Port	TCP port on which an implementation accepts TLS connections to exchange DICOM information.
Unique Identifier (UID)	A globally unique "dotted decimal" string that identifies a specific object or a class of objects; an ISO-8824 Object Identifier. Examples: Study Instance UID, SOP Class UID, SOP Instance UID.
User Agent	A client in a network protocol used in communications within a client-server distributed computing system. In particular, the Hypertext Transfer Protocol (HTTP) identifies the client software originating the request, using a user-agent header, even when the client is not operated by a user.
Value Representation (VR)	The format type of an individual DICOM data element, such as text, an integer, a person's name, or a code. DICOM information objects can be transmitted with either explicit identification of the type of each data element (Explicit VR), or without explicit identification (Implicit VR) ; with Implicit VR, the receiving application must use a DICOM data dictionary to look up the format of each data element.

[Modify: Add a list of product specific definitions here. If none are needed remove the following introduction and table]

The following list includes product specific definitions used throughout this Conformance Statement

Product-specific Term

This is a product specific term used throughout this Conformance Statement

N.3.5 Abbreviations

Abbreviations that are used in this DICOM Conformance Statement are listed here.

[It is important to add any additional terms used by the implementation. Terms in the list may also be deleted at the discretion of the implementer.]

AE	Application Entity
AET	Application Entity Title
CAD	Computer Aided Detection
CDA	Clinical Document Architecture
CID	Context Identifier
DCS	DICOM Conformance Statement
DHCP	Dynamic Host Configuration Protocol
DICOM	Digital Imaging and Communications in Medicine
ELE	Explicit VR Little Endian
FSC	File-Set Creator
FSU	File-Set Updater
FSR	File-Set Reader
IANA	Internet Assigned Numbers Authority
IHE	Integrating the Healthcare Enterprise
ILE	Implicit VR Little Endian
IOD	Information Object Definition
IPv4	Internet Protocol version 4
IPv6	Internet Protocol version 6
ISO	International Organization for Standardization
MPPS	Modality Performed Procedure Step
MWL	Modality Worklist
NEMA	National Electrical Manufacturers Association
NTP	Network Time Protocol
OID	Object Identifier
OS	Origin Server
PDU	Protocol Data Unit
PHI	Protected Health Information
PPS	Performed Procedure Step
QIDO-RS	Query based on ID for DICOM Objects by RESTful Services
RTV	Real-Time Video
SCP	Service Class Provider
SCU	Service Class User
SDP	Service Description Protocol
SOP	Service-Object Pair
SPS	Scheduled Procedure Step
SR	Structured Reporting
STOW-RS	STore Over the Web by RESTful Services
TCP/IP	Transmission Control Protocol/Internet Protocol
TID	Template Identifier
UA	User Agent
UI	User Interface
UID	Unique Identifier
UL	Upper Layer
UPS	Unified Procedure Step
UPS-RS	Unified Procedure Step by RESTful Services
VR	Value Representation
WADO-RS	Web Access to DICOM Objects by RESTful Services
WADO-URI	Web Access to DICOM Objects by URI

N.3.6 References

[Referenced documents should be listed here, including appropriate product manuals (such as service manuals that specify how to set DICOM communication parameters). References to the DICOM Standard should provide the URL for the free published version of the Standard, but should not specify a date of publication]:

[1] National Electrical Manufacturers Association (NEMA), Rosslyn, VA USA. PS3 / ISO 12052 Digital Imaging and Communications in Medicine (DICOM) Standard. http://www.dicomstandard.org .

[2] Integrating the Healthcare Enterprise (IHE). IHE Radiology Technical Framework. http://www.ihe.net/Resources/technical_frameworks/#radiology .

N.4 Implementation Model

[Provide a short description of your implementation, including list of product names and versions that this DICOM Conformance Statement (DCS) intends to cover, as well as the use of DICOM Networking, DICOM Media Interchange and DICOM Web Services to achieve their purpose.]

[Also provide some high-level details of your product architecture, which are relevant to the interoperability features of the product (e.g., implementation of functionality in separate applications).]

N.4.1 Application Entities and Data Flow

The network and media interchange application model for the < Product> is shown in Figure N.4-1 <Product> Application Data Flow Diagram.

[Edit the Application Data Flow Diagram and description below as appropriate. Note that the Real-World Activity and Application Entity names specified in the figure must be used consistently throughout the document. If your product supports configurable AE definition, then describe the default configuration of AEs in this section. As a reminder, an AE is a representation of the external behavior of an application process in terms of DICOM network services, web services and/or media exchange capabilities implemented in one or more roles. A single device may have multiple Application Entities.]

Figure N.4-1. <Product> Application Data Flow Diagram

[For each AE listed in Figure N.4-1 add one subsection A.4.1.x to describe the AE's DICOM functionality with regards to supported DIMSE, DICOM Web and Media Services, including the real-world activities that may trigger the service.]

[If your system supports flexible grouping of Services into Application Entities, keep the following paragraph, otherwise delete it]

This section describes the organization of the supported Services into Application Entities based on the default configuration of the system. This may change based on the actual setup at the customer site. See Section N.6 for details about the configurability of Services into AEs.

N.4.1.1 Functional Definition of <Application Entity 1>

[Provide a functional description of <Application Entity 1>, i.e., the DICOM Services (DIMSE, DICOM Web and Media Services), and supported roles, Real World Activities triggering the service and AE specific behavior.]

N.5 Service and Interoperability Description

N.5.1 Mapping of Services to Application Entities

Table N.5-1 provides an overview of the Application Entities and the Services supported by each AE.

[Table N.5-1 provides the mapping between Application Entities, Services and Roles as indicated in the example below.]

Table N.5-1. Service to AE Mapping

Application Entity	Supported Services	Role
		DIMSE		DICOM Web		DICOM Media			Real-Time Video
		SCU	SCP	Origin Server	User Agent	FSC	FSU	FSR	SCU	SCP
<Application Entity 1>	Basic Worklist Management
<Application Entity 1>	MPPS
<Application Entity 2>	Storage
	Storage Commitment
	Query/Retrieve
<Application Entity 3>(see Note 1)	Storage
<Application Entity 3>(see Note 1)	Query/Retrieve
<Application Entity 4>	Print Management
<Media Entity 1>	Media Storage
<RTV Entity 1>	Real-Time Video

[If needed, explain specific behavior of an AE in a note, e.g., if you have an AE that provides specifically storage of de-identified instances or support for querying rejected instances as defined in the IOCM profile, e.g.:

Note

This implementation of Query/Retrieve service handles retrieval of rejected instances as defined in the IHE Radiology IOCM Profile [2].

]

N.5.2 DIMSE Services

[The following sections define the details of the supported DIMSE Services in more details. Fill in the information for all services supported by the system. Tables are given as examples and should be modified to meet the functionality of the system.]

N.5.2.1 Basic Worklist Management Service

N.5.2.1.1 SCU of the Modality Worklist Information Model - FIND SOP Class

As a Service Class User of the Modality Worklist Information Model - FIND SOP Class, the <Product> uses the C-FIND-RQ message to query the SCP. It supports the Query Keys listed in Table N.5-2.

In the "Matching Type" column, the following Values can be used:

SINGLE_VALUE: SCU can request single Value matching on this Attribute.
UID: SCU can request List of UID matching on this Attribute.
WILDCARD: SCU can request Wildcard matching on this Attribute.
RANGE: SCU can request Range matching on this Attribute.
SEQUENCE: SCU can request sequence matching on this Attribute.
UNIVERSAL: SCU can request that the Attribute be a return Value (universal matching).

In the "Query Value Source" column, the following Values can be used:

FIXED: The query Value cannot be modified by the user or by configuration.
GENERATED: The query Value is generated by the system (e.g., current date as the study date).
CONFIGURATION: The query Value is dependent on system configuration.
USER: The query Value is entered by the user.
SCANNED: The query Value is read from a barcode scanner or similar device.
EMPTY: The query Value is sent with a zero-length Value to indicate it is a return key only.

In the "Display on UI" column the following Values can be used:

D: the return Value is displayed on the main UI by default.
C: the return Value is displayed on the main UI if configured.
N: the return Value is never displayed.

[Modify the Table N.5-2 to include all Attributes supported by your system and use the terms defined for Matching Type, Query Value Source and Display on UI above. If Display on UI Values are modified from the ones received, indicate in a footnote. If multiple Values are supported for the Query Value Source, list all of them.]

Table N.5-2. Supported C-FIND Query Parameters for Modality Worklist - SCU

Attribute Name	Tag	Matching Type	Query Value Source	Value	Display on UI	Comments
Scheduled Procedure Step
Scheduled Procedure Step Sequence	(0040,0100)	SEQUENCE
>Scheduled Station AE Title	(0040,0001)	SINGLE_VALUE	GENERATED		D	AE title of the system performing the query
>Scheduled Procedure StepStart date	(0040,0002)	RANGE	GENERATED		D	Current date and time minus 1 hour plus 24 hours ahead
>Scheduled Procedure StepStart Time	(0040,0003)	RANGE	GENERATED		D	Current date and time minus 1 hour plus 24 hours ahead
>Modality	(0008,0060)	SINGLE_VALUE	FIXED	CT
>Scheduled PerformingPhysician's Name	(0040,0006)	UNIVERSAL	EMPTY		D
…
Requested Procedure

Study Instance UID	(0020,000D)	UNIVERSAL	EMPTY
…
Imaging Service Request
Accession Number	(0008,0050)	SINGLE VALUE	USER		D	See Annex D for details
Issuer of Accession Number Sequence	(0008,0051)	UNIVERSAL	EMPTY
…
Visit Identification
…
Visit Status
…
Patient Identification
Patient's Name	(0010,0010)	WILDCARD	USER		D
…
Patient Demographics

[Describe scenarios in which the product can issue C-FIND-CANCEL Requests, e.g.,

The product issues C-FIND CANCEL requests in the following scenarios:* Configurable maximum of matches detected* Initiated by user]

[Also describe the SCU behavior if the cancellation request is ignored by the SCP and the SCP continues sending responses.]

[Document your product's query capabilities and behavior for handling non-default character sets, especially for handling person names (VR of PN), e.g.:

When configured for Japanese character set support, Person Name query attributes may contain ideographic (kanji) and/or phonetic (hiragana and katakana) and/or Romanized (romaji) representations.

When configured for Chinese character set support, Person Name query attributes may contain ideographic (hanzi) and/or phonetic (pinyin) representations are supported. For Patient’s Name (0010,0010), the representation which is displayed by default in the worklist is configurable.

When configured for Korean character set support, Person Name query attributes may contain ideographic (hanja) and/or phonetic (hangul) and/or Romanized representations.

If the product receives from the SCP a C-FIND response containing unsupported values in Specific Character Set (0008,0005), characters in that character set will be treated as unknown characters as described in Section 6.1.2.3 in PS3.5 .

If a Person Name attribute contains multiple representations, the GUI will display one representation based on a configurable order of preference.]

N.5.2.1.2 SCP of the Modality Worklist Information Model - FIND SOP Class

As a Service Class Provider of the Modality Worklist Information Model - FIND SOP Class, the <Product> uses the C-FIND-RSP to communicate matches back to the SCU. It supports the Matching Keys listed in Table N.5-3.

In the "Matching Type" column, the following Values can be used:

SINGLE_VALUE: SCP can perform single Value matching on this Attribute.
UID: SCP can perform List of UID matching on this Attribute.
WILDCARD: SCP can perform Wildcard matching on this Attribute.
RANGE: SCP can perform Range matching on this Attribute.
SEQUENCE: SCP can perform sequence matching on this Attribute.
UNIVERSAL: SCP can provide the Attribute in the C-FIND response (i.e., universal matching).

[Table N.5-3 contains a set of Attributes that could be supported by a product. Add and remove Attributes in order to match your product implementation using the matching type as defined above. If multiple codes are supported, list all of them. Use the "Comments" column if clarification is needed.]

Table N.5-3. Supported C-FIND Return Keys for Modality Worklist - SCP

Attribute Name	Tag	Matching Type
Scheduled Procedure Step
Schedule Procedure Step Sequence	(0040,0100)
>Scheduled Station AE Title	(0040,0001)	SINGLE_VALUE
>Scheduled Procedure StepStart Date	(0040, 0002)	RANGE
>Scheduled Procedure StepStart Time	(0040, 0003)	RANGE
>Modality	(0008,0060)	SINGLE_VALUE
>Scheduled PerformingPhysician's Name	(0040,0006)	WILDCARD
…
Requested Procedure
Study Instance UID	(0020,000D)	UNIVERSAL
…
Imaging Service Request
Accession Number	(0008,0050)	SINGLE_VALUE
Issuer of Accession Number Sequence	(0008,0051)	UNIVERSAL
Requesting Physician	(0032,1032)	UNIVERSAL
Referring Physician's Name	(0008,0090)	UNIVERSAL
…
Visit Identification
…
Visit Relationship
…
Patient Identification
…
Patient Demographics
…

[Describe the behavior of the product when it receives a C-FIND-CANCEL Request.]

[Document your product's query capabilities and behavior for handling non-default character sets, especially for handling person names (VR of PN), e.g.:

If the product receives from the SCU a Request Identifier containing unsupported values in the Specific Character Set (0008,0005), then no matching is performed and an error will be returned indicating the SCP is unable to process the request.]

[Document your product's query capabilities and behavior for handling implementation-dependent matching of VRs, such as for DA, DT, TM, IS and DS.]

N.5.2.2 Modality Performed Procedure Step Service

N.5.2.2.1 SCU of the Modality Performed Procedure Step SOP Class

As a Service Class User of the Modality Performed Procedure Step SOP Class, the <Product> supports the Attributes listed in Table N.5-4 in the N-CREATE-RQ and N-SET-RQ messages, if it creates the message.

In the "Source" column the following Values can be used:

FIXED: the Value is pre-defined and cannot be modified.
GENERATED: the Value is generated by the system.
CONFIGURATION: the Value is copied from system configuration.
MWL: the Value is copied from modality worklist entry.
USER: the Value is entered by the user.
SCANNED: the Value is read from a barcode scanner or similar device.
EMPTY: The Attribute is sent with a zero-length Value

[List all Attributes provided in the MPPS message and list the Values that are used to populate the N-CREATE or N-SET messages, add or remove Attributes as applicable for your product and note that in the "Source" column, multiple Values can be provided in a semicolon separated list.]

Table N.5-4. Supported N-CREATE and N-SET Attributes for Modality Performed Procedure Step - SCU

Attribute Name	Tag	Source	Value N-CREATE	Value N-SET
Specific Character Set	(0008,0005)	FIXED	ISO_IR 100	ISO_IR 100
Performed Procedure Step Relationship
Scheduled Step Attribute Sequence	(0040,0270)
>Study Instance UID	(0020,000D)	MWL
>Accession Number	(0008,0050)	MWL; USER; EMPTY
>Issuer of Accession Number Sequence	(0008,0051)	MWL; GENERATED
…
Patient's Name	(0010,0010)	MWL; USER
Patient ID	(0010,0020)	MWL; GENERATED
…
Performed Procedure Step Information
Performed Procedure Step ID	(0040,0253)
…
Performed Procedure Step Status	(0040,0252)	GENERATED	DISCONTINUED
Performed Procedure Step Discontinuation Reason Code Sequence		GENERATED		[Either reference CID 9301 or provide the supported Code Set, if the Performed Procedure Step Status is set to DISCONTINUED]
…
Image Acquisition Results
Modality	(0008,0060)	GENERATED	CT
Study ID	(0020,0010)	GENERATED	Copied from Requested Procedure ID
Performed Protocol Code Sequence	(0040,0260)	GENERATED
…

[Describe the triggers by which your product initiates sending messages, e.g., the N-CREATE is sent when starting image acquisition and N-SET is sent when the study is closed.]

[If product also supports forwarding of MPPS messages (e.g., as described by the MPPS Manager Actor in the IHE Schedule Workflow profile), provide a description of the product behavior here.]

N.5.2.2.2 SCP of the Modality Performed Procedure Step SOP Class

As a Service Class Provider of the Modality Performed Procedure Step SOP Class, the product receives N-CREATE-RQ and N-SET-RQ messages from a remote SCU indicating the status of a procedure.

[Indicate in Table N.5-5 whether your product has specific requirements with regards to the message content, e.g., whether specific Attributes are required using Y for yes and N for no.]

Table N.5-5 lists the message content that is required.

Table N.5-5. Supported N-CREATE and N-SET Attributes for Modality Performed Procedure Step - SCP

Attribute Name	Tag	Required in N-CREATE	Required in N-SET	Comments
Specific Character Set	(0008,0005)
Performed Procedure Step Relationship
Scheduled Step Attribute Sequence	(0040,0270)
>Study Instance UID	(0020,000D)
>Accession Number	(0008,0050)
>Issuer of Accession Number Sequence	(0008,0051)
Patient Name	(0010,0010)
Patient ID	(0010,0020)
…
Performed Procedure Step Information
Performed Procedure Step ID	(0040,0253)
Performed Procedure Step Discontinuation Reason Code Sequence	(0040,0281)
…
Image Acquisition Results
Modality	(0008,0060)
Study ID	(0020,0010)
Performed Protocol Code Sequence	(0040,0260)
…

[Describe the behavior of the product upon receiving an MPPS message, both the N-CREATE and the N SET.]

N.5.2.3 Unified Worklist and Procedure Step Service

[If your product supports any of the Unified Worklist SOP Classes, list the supported SOP Classes, the role, a list of supported messages, and the content of each supported message. If one or more of the Unified Worklist SOP Classes are not supported, keep the section, but include text indicating the SOP Class is "N/A".]

N.5.2.4 Instance Availability Notification Service

N.5.2.4.1 SCU of the Instance Availability Notification SOP Class

As a Service Class User of the Instance Availability Notification SOP Class, the system uses the N-CREATE-RQ message to inform remote SCPs about the availability and status of instances stored. Details of the message content are summarized in Table N.5-6.

In the "Source" column the following Values can be used:

FIXED: The Value is predefined and cannot be modified by data entry or by configuration.
GENERATED: The Value is generated by the system (e.g., current date as the study date).
CONFIGURATION: The Value is dependent on system configuration.
IMAGE: The Value is copied from the SOP Instance.
MWL: The Value is copied from Modality Worklist entry.
MPPS: The Value is copied from the MPPS message.

[Table N.5-6 lists some Attribute for instance availability notification as examples. Complete table with Attributes supported by your product. For the "Source" column use Values as defined above.]

Table N.5-6. Supported N-CREATE Attributes for Instance Availability Notification - SCU

Attribute Name	Tag	Source	Value
Specific Character Set	(0008,0005)	FIXED	ISO_IR 100
Referenced Performed Procedure Step Sequence	(0008,1111)	GENERATED
>…	(0008,1150)
>Performed Workitem Code Sequence	(0040,4019)	GENERATED
>>…
Study Instance UID	(0020,000D)	IMAGE
Referenced Series Sequence	(0008,1115)	IMAGE
>Series Instance UID	(0020,000E)	IMAGE
>Referenced SOP Sequence	(0008,1199)	IMAGE
>>…
>>Instance Availability	(0008,0056)	GENERATED	See Table N.5-7
>>Retrieve AE Title	(0008,0054)	CONFIGURATION
…

The <Product> supports the Values listed in Table N.5-7, for the Instance Availability (0018,0056) Attribute.

[Fill in Table N.5-7 with Values supported for the Instance Availability Attribute and define the meaning of these Values in the context of your <Product>]

Table N.5-7. Meaning of Instance Availability Values- SCU

Value	Meaning
ONLINE
NEARLINE
OFFLINE
UNAVAILABLE

[Describe the mechanism that triggers sending of an Instance Availability Notification, the frequency and retrieve capabilities for referenced instances.]

[Describe the relationship between the Instance Availability Notification and Performed Procedure Step SOP Class, if both are supported.]

N.5.2.4.2 SCP of the Instance Availability Notification SOP Class

As a Service Class Provider of the Instance Availability Notification SOP Class, the system receives the N-CREATE-RQ message containing information on the availability and status of instances stored.

Table N.5-8 describes the behavior of <Product> when encountering one of the following Values for the Instance Availability (0018,0056) Attribute.

[Fill in the table with Values supported for the Instance Availability Attribute and define the policies of the product upon encountering these Values.]

Table N.5-8. Behavior on Instance Availability Values -SCP

Value	Behavior
ONLINE
NEARLINE
OFFLINE
UNAVAILABLE

[Describe the relationship between the Instance Availability Notification and Performed Procedure Step SOP Class, if both are supported and if a relationship exists.]

N.5.2.5 Storage Service

N.5.2.5.1 SCU of the Storage SOP Classes

As a Service Class User of the Storage Service Class, the <Product> uses the C-STORE-RQ message to request storage of DICOM objects by a remote SCP. See Section N.1.1 Content and Transfer in the Overview for the list of supported SOP Classes.

For details regarding the content of SOP Instances that are created by the system, see Section N.9, which describes the underlying IOD of the supported SOP Classes.

[Provide some details regarding the triggering of storage requests (e.g., automatically when an instance is stored, automatically when the study is closed, or initiated by the user).]

[Describe when and how your product divides sets of instances into multiple series and or studies and how these are ordered.]

[Describe the behavior of your product in the case of a C-STORE operation using a referenced pixel data Transfer Syntax such as JPIP Referenced Pixel Data Transfer Syntax. This includes the duration of validity of the reference.]

N.5.2.5.1.1 Transcoding of Transfer Syntaxes

[For implementations that store locally using multiple Transfer Syntaxes and if the SCU includes multiple Transfer Syntaxes in each Presentation Context it negotiates, the following can provide a useful summary for assessing compatibility with receiving systems. If this information is not useful for your product, replace the content of this Section with the text "N/A" and append "- N/A" to the end of the section title.]

Table N.5-9 describes supported transcodings between the locally stored encoding of SOP Instances and the negotiated Transfer Syntax. The following Values can be used:

SUPPORTED: Transcoding is possible and same SOP Instance UID is re-used.
NEW_UID: Transcoding is possible; however a new SOP Instance is created for transfer, e.g., due to lossy compression.
NOT_SUPPORTED: Transcoding is not possible.

[Table N.5-9 shows an example of how this transcoding could look, modify and add columns and rows as needed for Transfer Syntaxes supported by your product. If you need to provide further details on specific transcoding those can be added as notes below the table.]

Table N.5-9. Transcoding of Transfer Syntaxes

Stored Transfer Syntax	Sent Transfer Syntax
Stored Transfer Syntax	Implicit VR Little Endian	Explicit VR Little Endian	JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14)	JPEG Baseline (Process 1)	…
Implicit VR Little Endian		SUPPORTED (see Note 1)	SUPPORTED	NEW_UID
Explicit VR Little Endian	SUPPORTED		SUPPORTED	NEW_UID
JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14)	SUPPORTED	SUPPORTED		NEW_UID
JPEG Baseline (Process 1)	NOT_SUPPORTED	NOT_SUPPORTED	NOT_SUPPORTED
ACME Private Transfer Syntax 1 (See Note 2)	NOT_SUPPORTED	SUPPORTED	NOT_SUPPORTED	NOT_SUPPORTED
…

Note

Explanation of the details of the transcoding (e.g., for known Private Attributes, the correct VR will be used. All others will be encoded as VR UN).
This Private Transfer Syntax is using Explicit VR Little Endian with compressed pixel data.

N.5.2.5.2 SCP of the Storage SOP Classes

As a Service Class Provider of the Storage Service Class, the <Product> receives the C-STORE-RQ message from remote SCUs. See Section N.1.1 Content and Transfer in the Overview for the list of supported SOP Classes.

Table N.5-10 defines the conformance levels of <Product>.

Table N.5-10. Levels of Conformance

Levels of Conformance	<<0, 1, or 2>>
Level of Digital Signature Support	<<1, 2, or 3>>

The <Product> coerces the Attributes listed in Table N.5-11 upon receiving them from other systems.

The "SOP Class UID" column indicates whether the coercion is applicable to specific SOP Classes or to "ALL" SOP Classes.

The "Type of Change" column defines the coercion done to the Attributes, the following Values can be used:

MODIFIED: The Value of the Attribute is changed; the new Value is described in the "New Value" column.
ADDED: The Attribute is added with the Value defined in the "New Value" column.
REMOVED: That Attribute is completely removed from the instance.

The "Condition" column defines the condition under which coercion is performed. The following Values can be used:

ALWAYS: Data coercion is performed on each instance of the specified SOP Class that is received by the system.
EXTERNAL: Data coercion is performed on instances received from systems external to the institution.
CONFIGURATION: Data coercion is performed based on system configuration.
OTHER: Data coercion is performed for other conditions. Details are defined in the "Comments" column.

[Table N.5-11 defines some examples on which data coercion can be performed. Add/remove scenarios as they apply to your product implementation. In case you use OTHER as a condition, the "Comments" column must be used to define the condition in further detail. It is recommended to include Attributes that are coerced in the Modified Attributes Sequence (0400,0550) of the Original Attributes Sequence (0400,0561), which is documented in Section N.9.1.1.]

Table N.5-11. Attribute Coercion by Storage SCP

Attribute Name	Tag	SOP Class UID	Type of Change	New Value	Condition	Comments
Patient ID	(0010,0020)	ALL	MODIFIED	Local Patient ID	EXTERNAL
Issuer of Patient ID	(0010,0021)	ALL	ADDED	Local site as Issuer	ALWAYS
Lossy Image Compression	(0028,2110)	ALL	ADDED	01	CONFIGURATION	If lossy compression is enabled on system
Patient Name	(0010,0010)	CT Image Storage (1.2.840.10008.5. 1.4.1.1.2)	MODIFIED	Pat_xxx (where xxx is a sequential number)	OTHER	Studies received through CLINICALTRIAL AE
…

Table N.5-12 lists any limitations on displaying or processing instances, e.g., display or processing of the respective SOP Instances is prevented by an unsupported Value for an Attribute or the absence of that Attribute.

[When a Limitation is based on multiple Attributes (e.g., images cannot be displayed, if they are lossless compressed and encoded as Photometric Interpretation RGB), the Attributes are listed each in a row and the "Comments" and "Effect" cells are merged as shown in the example below. The "Comments" column is used to explain as necessary. Also use this mechanism when documenting restrictions based on Private Attributes, e.g., list the Private Creator attribute as well as the Private Attribute.]

The "Effect" column describes what happens if the limitation is encountered. The following Values are used:

ND: Display is not possible
LD: Display is limited
NP: Processing is not possible
LP: Processing is limited
OT: Other effects described in the "Comments" column

[If there are no restrictions on display or processing requirements, replace the sentence above with No restriction to display or post processing apply.]

Table N.5-12. Display and Processing Limitations for Storage SCP

Limitation Case			Effect	Comments
Attribute Name	Tag	Value	Effect	Comments
CT Image Storage (1.2.840.10008.5.1.4.1.1.2)
Bits Stored	(0028,0101)	16	ND
Digital Mammography X-Ray Image - Storage for Processing (1.2.840.10008.5.1.4.1.1.1.2.1)
Detector ID	(0018,700A)	ABSENT	NP	Value needs to be present for Licensing purposes
MR Image Storage (1.2.840.10008.5.1.4.1.1.4)
Private Creator	(0009,00xx)	MyCompanyPrivateCreator	LD	Different Diffusion directions and B Factors are not recognized for Diffusion Images
Diffusion B Factor	(0009,xx01)	ABSENT
Diffusion Direction	(0009,xx02)	ABSENT
All SOP Classes
Transfer Syntax UID	(0002,0010)	1.2.840.10008.1.2.4.70	ND	Lossless compressed RGB images cannot be displayed
Photometric Interpretation	(0028,0004)	RGB	ND	Lossless compressed RGB images cannot be displayed

Table N.5-13 lists the actions performed upon receiving instances from a remote AE and the system behavior when certain conditions are encountered

[Fill in Table N.5-13 for details. The Table shows some examples which can be reused, modified, deleted, or extended based on your product implementation]

Table N.5-13. Behavior when storing Instances

Action upon Receiving	Condition	System Behavior
Perform Attribute Validation	Minor DICOM inconsistencies	Fix error and log warning message: Incorrect characters are replaced with "?" Attributes exceeding length of VR are truncated Type 2 Attributes not present are inserted with zero length
	Duplicate Instance	<Reject/Overwrite/Ignore> Instances
	DICOM Validation error	Send failure code on Association
	Success	Instances are stored in an internal database
Add to an existing study	Mismatch in patient identifying information detected	Instances are stored in an exception queue
Add to an existing study	Success	Instances are stored in a local database
Localize Patient Information	Patient mismatch detected	Instances are stored in an exception queue
Localize Patient Information	Success	Original patient identity information is copied to Other Patient ID Sequence (0010,1002) Instances are stored in an internal database.
Coerce non-patient-identifying Attributes	Success	Original Values of coerced Attributes are copied to the Original Attributes Sequence (0040,0561). Instances are stored in a local database
Evaluate Key Object Selection Document Title	Manifest	Use referenced data for cross-enterprise document sharing (IHE XDS-I).
	Rejected for Quality Reasons Rejected for Patient Safety Reasons	Only provide instances referenced in retrieval on a specialized AE title
	Incorrect Modality Workflist Entry	Hide instances from display and never provide in retrieve requests
	All other document titles	Display key images according to the specified title
…

Table N.5-14 describes how the SCP handles compression for stored instances.

The following Values are used in the "Behavior" column:

AS_IS: Images are stored as received.
CONFIGURATION: Images are compressed based on internal configuration settings.
OTHER: All other conditions, which are further described in the "Comments" column.

The Transfer Syntax is used to describe the compression mechanism applied.

Table N.5-14. Image Compression by Storage SCP

SOP Class		Behavior	Transfer Syntax
Digital Mammography X-Ray Image Storage - For Processing	1.2.840.10008.5.1.4.1.1.1.2.1	CONFIGU-RATION	JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14 [Selection Value 1])	1.2.840.10008.1.2.4.70
Video Photographic Image Storage	1.2.840.10008.5.1.4.1.1.77.1.4.1	CONFIGURATION	JPEG Baseline (Process 1)	1.2.840.10008.1.2.4.50
All other SOP Classes		AS_IS

[Describe the mechanism by which additional SOP Classes are dynamically supported.]

[Describe storage details noted in PS3.4 Section B.4.3.2.]

N.5.2.6 Storage Commitment Service

N.5.2.6.1 SCU of the Storage Commitment SOP Class

As a Service Class User of the Storage Commitment SOP Class, the <Product> uses the N-ACTION-RQ message to request storage commitment from a remote SCP. In turn, it receives N-EVENT-REPORT-RQ messages from the SCP indicating success or failure of the request.

[Provide a list of Storage SOP Classes for which the product requests storage commitment. Also indicate whether this is configurable.]

[If Storage Commitment is provided for all supported SOP Classes, you can provide a reference to the list of supported Storage SOP Classes in Section N.1.1]

As a Service Class User of the Storage Commitment Push Model SOP Classes the product supports committing all Storage SOP Classes listed in Section N.1.1 Content and Transfer are supported.

[If Storage Commitment is provided for a subset of all supported Storage SOP Classes, provide a list of those, and delete the paragraph above.]

[Specify whether your product supports the Storage Media File Set ID and UID Attributes in the N-ACTION-Request. If this is supported, also list the Media Application profiles supported in this context.]

[Describe whether your product supports receiving the N-EVENT-REPORT request on the same Association as the N-ACTION.]

[Document the Behavior of <product> upon receiving an N-EVENT-REPORT with an Event Type ID of 1, e.g.

Upon receiving an N-EVENT-REPORT with an Event Type of 1 Instances will be removed from system after a configurable amount of time or if space is needed]

Table N.5-15 lists the behavior of <Product> for each possible Failure Reason (0008,1197) in the Failed SOP Sequence (0008,1198) upon receiving an N-EVENT-REPORT request from the SCP with an Event Type ID of 2 (Storage Commitment Request Complete - Failures Exist).

[Fill in the behavior of your product upon encountering the Status Code. Note that for each code, that is listed in the table, a behavior needs to be provided. If your system does not support specific codes, list "Code is ignored by the system".]

Table N.5-15. Failure Behavior for Storage Commitment SCU

Status Code	Description	Behavior
0110	Processing failure: A general failure in processing the operation was encountered.	The request for storage commitment is marked as failed. A warning is displayed if the user tries to delete affected instances
0112	No such object instance: One or more of the elements in the Referenced SOP Instance Sequence was not available.	The instance is re-sent, and the N-ACTION request is repeated.
0119	Class / Instance conflict: The SOP Class of an element in the Referenced SOP Instance Sequence did not correspond to the SOP Class registered for this SOP Instance at the SCP.	Code is ignored by the system
0122	Referenced SOP Class not supported: Storage Commitment has been requested for a SOP Instance with a SOP Class that is not supported by the SCP.	The request for storage commitment is marked as failed. A warning is displayed if the user tries to delete affected instances
0131	Duplicate Transaction UID: The Transaction UID of the Storage Commitment Request is already in use.	The request for storage commitment is marked as failed. A warning is displayed if the user tries to delete affected instances
0213	Resource limitation: The SCP does not currently have enough resources to store the requested SOP Instance(s).	The request for storage commitment is marked as failed. A warning is displayed if the user tries to delete affected instances

[Describe your product behavior in case the N-EVENT-REPORT request is not received after a specific time, e.g., <Product> expects to receive the N-EVENT-REPORT request in a configurable time frame after the N-ACTION is sent. If the N-EVENT-REPORT is not received within this configurable timeframe it repeats the N-ACTION-REQUEST.]

[Describe the policies for deleting instances from your product, both upon successful storage commitment as well as in failure scenarios.]

N.5.2.6.2 SCP of the Storage Commitment SOP Class

As a Service Class Provider of the Storage Commitment SOP Class, the <Product> receives the N-ACTION-RQ message to request storage commitment from a remote SCU. In turn it initiates the N-EVENT_REPORT-RQ messages to the SCU indicating success or failure of the request.

[Describe whether your product supports sending the N-EVENT-REPORT request on the same Association as the N-ACTION.]

Table N.5-16 lists conditions upon which an error code is sent in the Failure Reason (0008,1197) Attribute in the Failed SOP Sequence (0008,1198) of the N-EVEN-REPORT request.

[Fill in the conditions under which your product is sending the listed Status Codes. Note that for each code listed in the table, a condition needs to be provided. If your system does not support specific codes, list "Code is not supported"]

Table N.5-16. Failure Conditions on Storage Commitment SCP

Status Code	Description	Conditions
0110	Processing failure: A general failure in processing the operation was encountered.
0112	No such object instance: One or more of the elements in the Referenced SOP Instance Sequence was not available.
0119	Class / Instance conflict: The SOP Class of an element in the Referenced SOP Instance Sequence did not correspond to the SOP Class registered for this SOP Instance at the SCP.
0122	Referenced SOP Class not supported: Storage Commitment has been requested for a SOP Instance with a SOP Class that is not supported by the SCP.
0131	Duplicate Transaction UID: The Transaction UID of the Storage Commitment Request is already in use.
0213	Resource limitation: The SCP does not currently have enough resources to store the requested SOP Instance(s).

[Specify whether the Retrieve AE title Attribute is supported and if so, what policies exist for its usage.]

[Describe the policies and nature of commitment of the product, e.g., the duration of storage, retrieve capabilities, latency, capacity, and other pertinent information.]

[Describe how long the product typically needs to send the N-EVENT-REPORT-RQ after the N-ACTION-RQ is received.]

N.5.2.7 Query/Retrieve Service Class

[The sections below define some of the most used Query Retrieve SOP Classes as examples, however, there are many more Query/Retrieve SOP Classes defined in DICOM PS 3.4. If your product supports any of these additional SOP Classes, add additional Sections for these SOP Classes for SCU and SCP using the structure as indicated for any of the SOP Classes below.]

N.5.2.7.1 SCU of the Study Root Q/R Information Model - FIND SOP Class

As a Service Class User of the Study Root Q/R - Information Model - FIND SOP Class, the <Product> uses the C-FIND-RQ message and supports the Query Keys listed in Table N.5-17 for hierarchical queries.

In the "Matching Type" column the following Values can be used:

SINGLE_VALUE: SCU can request Single Value matching on this Attribute.
UID: SCU can request List of UID matching on this Attribute.
WILDCARD: SCU can request Wildcard matching on this Attribute.
RANGE: SCU can request Range matching on this Attribute.
SEQUENCE: SCU can request Sequence matching on this Attribute.
UNIVERSAL: SCU can request that the Attribute be a return Value (universal matching).

In the "Query Value Source" column the following Values can be used:

FIXED: The query Value cannot be modified by the user or by configuration.
GENERATED: The query Value is generated by the system (e.g., current date as the study date).
CONFIGURATION: The query Value is dependent on system configuration.
USER: The query Value is entered by the user.
SCANNED: The query Value is read from a barcode scanner or similar device.
EMPTY: The query Value is sent with a zero-length value to indicate it is a return key only.

In the "Display on UI" column the following Values can be used:

D: the return Value is displayed on the main UI by default.
C: the return Value is displayed on the main UI if configured.
N: the return Value is never displayed.

[Modify Table N.5-17 to include all Attributes supported by your system (standard Attributes as well as private Attributes) and use the terms defined for matching type, query Value source and Display on UI above. If multiple codes are supported, list all of them.]

Table N.5-17. Supported C-FIND Attribute Matching for Study Root Q/R Model -SCU

Attribute Name	Tag	Matching Type	Query Value Source	Display on UI
Study Level
Study Date	(0008,0020)	RANGE	USER	D
Study Time	(0008,0030)	RANGE	USER	D
Accession Number	(0008,0050)	SINGLE_VALUE	USER	D
Patient's Name	(0010,0010)	WILDCARD	USER	D
Patient ID	(0010,0020)	SINGLE_VALUE	USER, GENERATED	D
Study Instance UID	(0020,000D)	UNIVERSAL	EMPTY	N
Modalities in Study	(0008,0061)	SINGLE_VALUE	USER	D
Study Description	(0008,1030)	WILDCARD	USER	D
…
Series Level
Modality	(0008,0060)	SINGLE_VALUE	USER	D
Body Part Examined	(0018,0015)	SINGLE_VALUE	USER	C
…
Instance Level
…
Private Attributes
Private Creator	(0009,0010)	SINGLE_VALUE	FIXED	N
Private Value1	(0009,1001)	UNIVERSAL	EMPTY	C
…

[If <product> supports Extended Negotiation for Relational Queries, describe supported matching Attributes.]

[Describe scenarios in which the SCU can issue C-FIND-CANCEL Requests, e.g.

The product issues C-FIND CANCEL requests in the following scenarios:* Configurable maximum of matches detected* Initiated by user]

[Also describe the behavior if the SCP ignores the cancellation request and continues sending responses.]

[Document your product's query capabilities and behavior for handling non-default character sets, especially for handling person names (VR of PN), e.g.:

When configured for Japanese character set support, Person Name query attributes may contain ideographic (kanji) and/or phonetic (hiragana and katakana) and/or Romanized (romaji) representations.

When configured for Korean character set support, Person Name query attributes may contain ideographic (hanja) and/or phonetic (hangul) and/or Romanized representations.

If a Person Name attribute contains multiple representations, the GUI will display one representation based on a configurable order of preference.]

N.5.2.7.2 SCU of the Patient Root Q/R Information Model - FIND SOP Class

[If this SOP Class is supported, fill in the section as indicated in Section N.5.2.7.1.]

N.5.2.7.3 SCU of the Study Root Q/R Information Model - MOVE SOP Class

[Describe if List of UID matching may be used to retrieve multiple entities at STUDY, SERIES, or IMAGES levels.]

[Also specify the conditions under which a C-MOVE CANCEL may be sent.]

[Indicate whether your product supports sending matching instances to a different AE Title.]

[Indicate your product behavior in case no C-STORE Request is received after a specific time, e.g., <Product> expects to receive the C-STORE Request in a configurable time frame after the C-MOVE Request is sent. If no C-STORE Requests are received within this configurable timeframe, it repeats the C-MOVE-Request.]

N.5.2.7.4 SCU of the Patient Root Q/R Information Model - MOVE SOP Class

[If this SOP Class is supported, fill in the section as indicated in Section N.5.2.7.3.]

N.5.2.7.5 SCP of the Study Root Q/R Information Model - FIND SOP Class

As a Service Class Provider of the Study Root Q/R - Information Model - FIND SOP Class, the <Product> uses the C-FIND-RSP to communicate matches back to the SCU. It supports the Matching Keys listed in Table N.5-18 for hierarchical queries.

In the "Matching Type" column, the following Values can be used:

SINGLE_VALUE: SCP can perform single Value matching on this Attribute.
UID: SCP can perform List of UID matching on this Attribute.
WILDCARD: SCP can perform Wildcard matching on this Attribute.
RANGE: SCP can perform Range matching on this Attribute.
SEQUENCE: SCP can perform sequence matching on this Attribute.
UNIVERSAL: SCP can provide the Attribute in the C-FIND response (universal matching).

[Table N.5-18 contains a set of Attributes (standard Attributes as well as private Attributes) that could be supported by a product. Add and remove Attributes in order to match your product implementation using the matching type as defined above. If multiple codes are supported, list all of them. Use the "Comments" column if clarification is needed.]

Table N.5-18. Supported C-FIND Attribute Matching for Study Root Q/R Model - SCP

Attribute Name	Tag	MatchingType
Study Level
Study Date	(0008,0020)	RANGE
Patient's Name	(0010,0010)	WILDCARD
Patient ID	(0010,0020)	SINGLE_VALUE
Study Instance UID	(0020,000D)	UNIVERSAL
Modalities in Study	(0008,0061)	SINGLE_VALUE
Study Description	(0008,1030)	WILDCARD
…
Series Level
…
Instance Level
…
Private Attributes
…

[If <product> supports Extended Negotiation for Relational Queries, describe supported matching Attributes.]

[Document your product behavior in case you are encountering non supported private Attributes.]

[Describe the behavior of the product if it receives a C-FIND-CANCEL Request.]

[Document your product's query capabilities and behavior for handling non-default character sets, especially for handling person names (VR of PN), e.g.:

[Document your product's query capabilities and behavior for handling implementation-dependent matching of VRs, such as for DA, DT, TM, IS and DS.]

[If your product supports Extended Negotiation for fuzzy semantic matching of person names describe how matching is performed, e.g., whether your matching is insensitive to case, position, accent, or character encoding, or whether you support phonetic matching.]

N.5.2.7.6 SCP of the Patient Root Q/R Information Model - FIND SOP Class

[If this SOP Class is supported, fill in the section as indicated in Section N.5.2.7.5.]

N.5.2.7.7 SCP of the Study Root Q/R Information Model - MOVE SOP Class

As the SCP of the Study Root Q/R - Information Model - MOVE, the <Product> receives the C-MOVE-RQ and in turn uses the C-STORE-RQ sub operation to send matching SOP Instances to the Move Destination AE included in the C-MOVE-RQ.

[Provide a list of Storage SOP Classes supported or reference Storage Table in Overview e.g.]

As the SCP of the Storage Service Class, all Storage SOP Classes listed in Section N.1.1 are supported.

[Describe the relationship between the incoming C-MOVE Request and the C-STORE Sub-operation, e.g., is each instance sent on one Association or is the same Association used for all instances, is this behavior configurable.]

[Describe your product behavior if a C-MOVE-CANCEL Request is received.]

N.5.2.7.8 SCP of the Patient Root Q/R - Information Model - MOVE SOP Class

[If this SOP Class is supported, fill in the section as indicated in Section N.5.2.7.7.]

N.5.2.8 Print Management Service

N.5.2.8.1 SCU of the Basic Grayscale Print Management Meta SOP Class

The Basic Grayscale Print Management Meta SOP Class is composed of the mandatory SOP Classes listed in Table N.5-19.

Table N.5-19. Basic Grayscale Print Management Meta SOP Classes - SCU

SOP Class Name	SOP Class UID
Basic Film Session	1.2.840.10008.5.1.1.1
Basic Film Box	1.2.840.10008.5.1.1.2
Basic Grayscale Image Box	1.2.840.10008.5.1.1.4
Printer	1.2.840.10008.5.1.1.16

N.5.2.8.1.1 Basic Film Session SOP Class

Table N.5-20 lists the supported DIMSE Services for the Basic Film Session SOP Class:

[List the supported DIMSE Service Elements. Remove the non-supported ones.]

Table N.5-20. Services for the Basic Film Session SOP Class - SCU

DIMSE Service Element	Purpose
N-CREATE	Create the Film Session
N-SET	Update the Film Session
N-DELETE	Delete the Film Session
N-ACTION	Print all Film Boxes in the Film Session

Table N.5-21 lists the supported N-CREATE and N-SET Attributes for Basic Film Session:

[List the supported Attributes and their possible values / ranges. List the default Value when relevant. All tags are optional for the SCU in the Basic Film session. See example below.]

Table N.5-21. Supported N-CREATE and N-SET Attributes for the Basic Film Session SOP Class - SCU

Attribute Name	Tag	Values	Default
Number of Copies	(2000,0010)	<range or fixed Value>	1
Print Priority	(2000,0020)	<<HIGH LOW MED>>	LOW
Medium Type	(2000,0030)	<<BLUE FILM CLEAR FILM MAMMO BLUE FILM MAMMO CLEAR FILM PAPER …>>
Film Destination	(2000,0040)	<<MAGAZINE PROCESSOR BIN_I …>>	PROCESSOR
Film Session Label	(2000,0050)
Memory Allocation	(2000,0060)
Owner ID	(2100,0160)

N.5.2.8.1.2 Basic Film Box SOP Class

Table N.5-22 lists the supported DIMSE Services for the Basic Film Box SOP Class:

[List the supported DIMSE Service Elements. Remove the non-supported ones.]

Table N.5-22. Supported Services for the Basic Film Box SOP Classes

DIMSE Service Element	Purpose
N-CREATE	Create the Film Box in a previously created Film Session
N-ACTION	Print the Film Box
N-SET	Update the Film Box
N-DELETE	Delete the Film Box

Table N.5-23 lists the supported N-CREATE and N-SET Attributes for Basic Film Box:

[List the supported Attributes and their possible Values. Provide the default Value when relevant. See example below.]

Table N.5-23. Supported N-CREATE and N-SET Attributes for the Basic Film Box SOP Class - SCU

Attribute Name	Tag	Values	Default
Image Display Format	(2010,0010)	<<STANDARD\C,R ROW\R1,R2,R3, etc. COL\C1,C2,C3, etc. SLIDE SUPERSLIDE CUSTOM\i>>	STANDARD\1,1
Annotation Display Format ID	(2010,0030)	Possible Values to be provided by the printer manufacturer
Film Orientation	(2010,0040)	<<PORTRAIT LANDSCAPE>>	PORTRAIT
Film Size ID	(2010,0050)	<<8INX10IN 8_5INX11IN 10INX12IN 11INX14IN 11INX17IN 14INX14IN 14INX17IN 24CMX24CM 24CMX30CM A4 A3 …>>
Magnification Type	(2010,0060)	<<REPLICATE BILINEAR CUBIC NONE …>>	CUBIC
Smoothing Type	(2010,0080)	<possible Values or range>
Border Density	(2010,0100)	<<BLACK WHITE i, where i represents the desired density in hundredths of OD …>>	BLACK
Empty Image Density	(2010,0110)	<<BLACK WHITE i, where i represents the desired density in hundredths of OD …>>	BLACK
Minimum Density	(2010,0120)	<possible Values or range in hundredths of OD>
Maximum Density	(2010,0130)	<possible Values or range in hundredths of OD>	300
Trim	(2010,0140)	<<YES NO>>	NO
Configuration Information	(2010,0150)
Illumination	(2010,015E)	<possible Values or range>	2000
Reflective Ambient Light	(2010,0160)	<possible Values or range>	10
Referenced Film Session Sequence	(2010,0500)	<possible Values or range>
>Referenced SOP Class UID	(0008,1150)	1.2.840.10008.5.1.1.1
>Referenced SOP Instance UID	(0008,1155)
Referenced Presentation LUT Sequence	(2050,0500)
>Referenced SOP Class UID	(0008,1150)	1.2.840.10008.5.1.1.23
>Referenced SOP Instance UID	(0008,1155)

N.5.2.8.1.3 Basic Grayscale Image Box SOP Class

Table N.5-24 lists the supported DIMSE Service for the Basic Grayscale Image Box SOP Class:

Table N.5-24. Services for the Basic Grayscale Image Box SOP Class

DIMSE Service Element	Purpose
N-SET	Set Image Attributes for a previously created Film Box

Table N.5-25 lists the supported N-SET Attributes for Basic Grayscale Image Box:

[List the supported Attributes and their possible Values. Provide the default Value when relevant. See example below.]

Table N.5-25. Supported N-SET Attributes for the Basic Grayscale Image Box SOP Class -SCU

Attribute Name	Tag	Values	Default
Magnification Type	(2010,0060)	<<REPLICATE BILINEAR CUBIC NONE …>>	CUBIC
Smoothing Type	(2010,0080)	<possible Values or range>	143
Minimum Density	(2010,0120)	<possible Values or range in hundredths of OD>
Maximum Density	(2010,0130)	<possible Values or range in hundredths of OD>	300
Configuration Information	(2010,0150)
Image Box Position	(2020,0010)	<possible Position Values or range>
Polarity	(2020,0020)	<<NORMAL REVERSE>>	NORMAL
Requested Image Size	(2020,0030)	width, x-dimension, in mm
Requested Decimate/Crop Behavior	(2020,0040)	<<DECIMATE CROP FAIL>>
Basic Grayscale Image Sequence	(2020,0110)
>Samples per Pixel	(0028,0002)	1
>Photometric Interpretation	(0028,0004)	<<MONOCHROME1 MONOCHROME2>>
>Rows	(0028,0010)
>Columns	(0028,0011)
>Pixel Aspect Ratio	(0028,0034)		1\1
>Bits Allocated	(0028,0100)	<<8 16>>
>Bits Stored	(0028,0101)	<<8 12>>
>High Bit	(0028,0102)	<<7 11>>
>Pixel Representation	(0028,0103)	0	0
>Pixel Data	(7FE0,0010)
Referenced Presentation LUT Sequence	(2050,0500)
>Referenced SOP Class UID	(0008,1150)	1.2.840.10008.5.1.1.23
>Referenced SOP Instance UID	(0008,1155)

N.5.2.8.1.4 Printer SOP Class

Table N.5-26 lists the supported DIMSE Services for the Printer SOP Class:

[List the supported DIMSE Service Elements. Remove the non-supported ones.]

Table N.5-26. Services for the Printer SOP Class

DIMSE Service Element	Purpose
N-EVENT-REPORT	Report the printer status in an asynchronous way
N-GET	Retrieve printer information and status.

An N-EVENT-REPORT request can be received by the SCU at any time during an Association.

Table N.5-27 summarizes the behavior of the SCU when receiving Event Types within the N-EVENT-REPORT.

Table N.5-27. Printer SOP Class N-EVENT-REPORT Behavior

Event Type Name	Event Type ID	Behavior
Normal	1
Warning	2
Failure	3

[Remove the following text and table if N-GET is not supported.]

Table N.5-28 lists the supported N-GET Attributes for Printer SOP Class:

[List the supported Attributes and the behavior of the SCU when receiving Printer Status / Printer status info. Remove the non-supported Attributes from the table.]

Table N.5-28. Supported N-GET Attributes for the Printer SOP Class - SCU

Attribute Name	Tag	Behavior
Printer Status	(2110,0010)	<<NORMAL WARNING FAILURE>>
Printer Status Info	(2110,0020)
Printer Name	(2110,0030)
Manufacturer	(0008,0070)
Manufacturer Model Name	(0008,1090)
Device Serial Number	(0018,1000)
Software Versions	(0018,1020)
Date Last Calibration	(0018,1200)
Time Last Calibration	(0018,1201)

N.5.2.8.2 SCU of the Basic Color Print Management Meta SOP Class

The Basic Color Print Management Meta SOP Class is composed of the mandatory SOP Classes listed in Table N.5-29:

Table N.5-29. Basic Color Print Management Meta SOP Classes

SOP Class Name	SOP Class UID
Basic Film Session	1.2.840.10008.5.1.1.1
Basic Film Box	1.2.840.10008.5.1.1.2
Basic Color Image Box	1.2.840.10008.5.1.1.4.1
Printer	1.2.840.10008.5.1.1.16

N.5.2.8.2.1 Basic Film Session SOP Class

[If your system also supports the Basic Grayscale Print Management Meta SOP Class and the Film Session parameters are identical for color, see Section N.5.2.8.1.1 Basic Film Session SOP Class for Basic Grayscale Print Management Meta SOP Class. Otherwise, copy the Film Session table here and fill in the proper Values.]

N.5.2.8.2.2 Basic Film Box SOP Class

[If your system also supports the Basic Grayscale Print Management Meta SOP Class and the Film Box parameters are identical for color, see Section N.5.2.8.1.2 Basic Film Box SOP Class for Basic Grayscale Print Management Meta SOP Class. Otherwise copy the Film Box table here and fill in the proper Values.]

N.5.2.8.2.3 Basic Color Image Box SOP Class

Table N.5-30 lists the supported DIMSE Service for the Basic Color Image Box SOP Class:

Table N.5-30. Services for the Basic Color Image Box SOP Class - SCU

DIMSE Service Element	Purpose
N-SET	Set each Image Attributes for a previously created Film Box

Table N.5-31 lists the supported N-SET Attributes for Basic Color Image Box:

[List the supported Attributes and their possible Values. Provide the default Value when relevant. See example below.]

Table N.5-31. Supported N-SET Attributes for the Basic Color Image Box SOP Class - SCU

Attribute Name	Tag	Values	Default
Magnification Type	(2010,0060)	<<REPLICATE BILINEAR CUBIC NONE …>>	CUBIC
Smoothing Type	(2010,0080)	<possible Values or range>	143
Image Box Position	(2020,0010)	<possible Position Values or range>
Polarity	(2020,0020)	<<NORMAL REVERSE>>	NORMAL
Requested Image Size	(2020,0030)	width, x-dimension, in mm
Requested Decimate/Crop Behavior	(2020,0040)	<<DECIMATE CROP FAIL>>
Basic Color Image Sequence	(2020,0111)
>Samples per Pixel	(0028,0002)	3
>Photometric Interpretation	(0028,0004)	RGB
>Planar Configuration	(0028,0006)	1 (frame interleave)
>Rows	(0028,0010)
>Columns	(0028,0011)
>Pixel Aspect Ratio	(0028,0034)		1\1
>Bits Allocated	(0028,0100)	8
>Bits Stored	(0028,0101)	8
>High Bit	(0028,0102)	7
>Pixel Representation	(0028,0103)	0
>Pixel Data	(7FE0,0010)

N.5.2.8.2.4 Printer SOP Class

[If your system also supports the Basic Grayscale Print Management Meta SOP Class, see 'Printer SOP Class' for 'Basic Grayscale Print Management Meta SOP Class' in Section N.5.2.8.1.4. Otherwise copy the Printer SOP Class table here and fill in the proper Values.]

N.5.2.8.3 SCU of the Basic Annotation Box SOP Class

Table N.5-32 lists the supported DIMSE Service for the Basic Annotation Box SOP Class:

Table N.5-32. Services for the Basic Annotation Box SOP Class - SCU

DIMSE Service Element	Purpose
N-SET	Set each image Attributes for a previously created Film Box

Table N.5-33 lists the supported N-SET Attributes for the Basic Annotation Box SOP Class:

[List the supported Attributes and their possible Values. Provide the default Value when relevant. See example below.]

Table N.5-33. Supported N-SET Attributes for the Basic Annotation Box SOP Class-SCU

Attribute Name	Tag	Values	Default
Annotation Position	(2030,0010)	1 to 6
Text String	(2030,0020)	Free text

N.5.2.8.4 SCU of the Print Job SOP Class

Table N.5-34 lists the supported DIMSE Services for the Print Job SOP Class:

[List the supported DIMSE Service Elements. Remove the non-supported one.]

Table N.5-34. Services for the Print Job SOP Class - SCU

DIMSE Service Element	Purpose
N-EVENT-REPORT	Report the printer status in an asynchronous way
N-GET	Retrieve printer information and status.

An N-EVENT-REPORT request can be received by the SCU at any time during an Association if the Print Job SOP Class has been negotiated by the SCU.

Table N.5-35 summarizes the behavior of the SCU when receiving Event Types within the N-EVENT-REPORT.

Table N.5-35. Print Job SOP Class N-EVENT-REPORT Behavior

Event Type Name	Event Type ID	Behavior
Pending	1
Printing	2
Done	3
Failure	4

[Remove the following text and table if N-GET is not supported.]

Table N.5-36 lists the supported N-GET Attributes for Print Job SOP Class:

[List the supported Attributes and the behavior of the SCU when receiving Execution Status / Execution Status Info. Remove the non-supported Attributes from the table.]

Table N.5-36. Supported N-GET Attributes for the Print Job SOP Class - SCU

Attribute Name	Tag	Behavior
Print Priority	(2000,0020)
Execution Status	(2100,0020)	<<PENDING PRINTING DONE FAILURE>>
Execution Status Info	(2100,0030)
Creation Date	(2100,0040)
Creation Time	(2100,0050)
Originator	(2100,0070)
Printer Name	(2110,0030)

N.5.2.8.5 SCU of the Presentation LUT SOP Class

Table N.5-37 lists the supported DIMSE Services for the Presentation LUT SOP Class:

[List the supported DIMSE Service Elements. Remove the non-supported one.]

Table N.5-37. Services for the Presentation LUT SOP Class - SCU

DIMSE Service Element	Purpose
N-CREATE	Create the Presentation LUT Instance
N-DELETE	Delete the Presentation LUT Instance

Table N.5-38 lists the supported N-CREATE Attributes for Presentation LUT:

[List the supported Attributes. Either Presentation LUT Sequence or Presentation LUT Shape must be present (not both).]

Table N.5-38. Supported N-CREATE Attributes for the Presentation LUT SOP Class-SCU

Attribute Name	Tag	Values
Presentation LUT sequence	(2050,0010)
> LUT Descriptor	(0028,3002)
> LUT Explanation	(0028,3003)
> LUT Data	(0028,3006)
Presentation LUT Shape	(2050,0020)	<<IDENTITY LIN OD>>

N.5.2.8.6 SCU of the Printer Configuration Retrieval SOP Class

Table N.5-39 lists the supported DIMSE for the Printer Configuration Retrieval SOP Class:

Table N.5-39. Services for the Printer Configuration Retrieval SOP Class - SCU

DIMSE Service Element	Purpose
N-GET	Retrieve printer configuration.

N.5.2.8.7 SCP of the Basic Grayscale Print Management Meta SOP Class

The Basic Grayscale Print Management Meta SOP Class is composed of the mandatory SOP Classes listed in Table N.5-40:

Table N.5-40. Basic Grayscale Print Management Meta SOP Classes - SCP

SOP Class Name	SOP Class UID
Basic Film Session	1.2.840.10008.5.1.1.1
Basic Film Box	1.2.840.10008.5.1.1.2
Basic Grayscale Image Box	1.2.840.10008.5.1.1.4
Printer	1.2.840.10008.5.1.1.16

N.5.2.8.7.1 Basic Film Session SOP Class

Table N.5-41 lists the supported DIMSE Services for the Basic Film Session SOP Class:

[List the supported DIMSE Service Elements. Remove the non-supported one.]

Table N.5-41. Services for the Basic Film Session SOP Class - SCP

DIMSE Service Element	Purpose
N-CREATE	Create the Film Session
N-SET	Update the Film Session
N-DELETE	Delete the Film Session
N-ACTION	Print all Film Boxes in the Film Session

Table N.5-42 lists the supported N-CREATE and N-SET Attributes for Basic Film Session:

[List the supported Attributes and their possible values/ranges. Indicate the default Value when relevant. See example below.]

Table N.5-42. - Supported N-CREATE and N-SET Attributes for Basic Film Session - SCP

Attribute Name	Tag	Values	Default
Number of Copies	(2000,0010)	<range or fixed Value>	1
Print Priority	(2000,0020)	<<HIGH LOW MED>>	LOW
Medium Type	(2000,0030)	<<BLUE FILM CLEAR FILM MAMMO BLUE FILM MAMMO CLEAR FILM PAPER …>>
Film Destination	(2000,0040)	<<MAGAZINE PROCESSOR BIN_I …>>	PROCESSOR
Film Session Label	(2000,0050)
Memory Allocation	(2000,0060)
Owner ID	(2100,0160)

[If the SCP supports N-ACTION for the Film Session SOP Class, then the SCP must specify the maximum number of collated films.]

N.5.2.8.7.2 Basic Film Box SOP Class

Table N.5-43 lists the supported DIMSE Services for the Basic Film Box SOP Class:

[List the supported DIMSE Service Elements. Remove the non-supported one.]

Table N.5-43. Services Supported for the Basic Film Box SOP Class - SCP

DIMSE Service Element	Purpose
N-CREATE	Create the Film Box in a previously created Film Session
N-ACTION	Print the Film Box
N-DELETE	Delete the Film Box
N-SET	Update the Film Box

Table N.5-44 lists the supported N-CREATE and N-SET Attributes for Basic Film Box:

[List the supported Attributes and their possible Values. Indicate the default Value when relevant. See example below.]

Table N.5-44. Supported N-CREATE and N-SET Attributes for Basic Film Box - SCP

Attribute Name	Tag	Values	Default
Image Display Format	(2010,0010)	<<STANDARD\C,R ROW\R1,R2,R3, etc. COL\C1,C2,C3, etc. SLIDE SUPERSLIDE CUSTOM\i>>	STANDARD\1,1
Annotation Display Format ID	(2010,0030)	<Possible Values>
Film Orientation	(2010,0040)	<<PORTRAIT LANDSCAPE>>	PORTRAIT
Film Size ID	(2010,0050)	<<8INX10IN 8_5INX11IN 10INX12IN 11INX14IN 11INX17IN 14INX14IN 14INX17IN 24CMX24CM 24CMX30CM A4 A3 …>>
Magnification Type	(2010,0060)	<<REPLICATE BILINEAR CUBIC NONE …>>	CUBIC
Smoothing Type	(2010,0080)	<possible Values or range>	143
Border Density	(2010,0100)	<<BLACK WHITE i, where i represents the desired density in hundredths of OD …>>	BLACK
Empty Image Density	(2010,0110)	<<BLACK WHITE i, where i represents the desired density in hundredths of OD …>>	BLACK
Minimum Density	(2010,0120)	<possible Values or range in hundredths of OD>	20
Maximum Density	(2010,0130)	<possible Values or range in hundredths of OD>	320
Trim	(2010,0140)	<<YES NO>>	NO
Configuration Information	(2010,0150)
Illumination	(2010,015E)	<possible Values or range>	2000
Reflective Ambient Light	(2010,0160)	<possible Values or range>	10
Referenced Film Session Sequence.	(2010,0500)
> Referenced SOP Class UID	(0008,1150)	1.2.840.10008.5.1.1.1
> Referenced SOP Instance UID	(0008,1155)
Referenced Image Box Sequence	(2010,0510)	Provided in the N-CREATE-RSP
> Referenced SOP Class UID	(0008,1150)	1.2.840.10008.5.1.1.4
> Referenced SOP Instance UID	(0008,1155)
Referenced Annotation Box Sequence	(2010,0520)
> Referenced SOP Class UID	(0008,1150)	1.2.840.10008.5.1.1.15
> Referenced SOP Instance UID	(0008,1155)
Referenced Presentation LUT Sequence	(2050,0500)
> Referenced SOP Class UID	(0008,1150)	1.2.840.10008.5.1.1.23
> Referenced SOP Instance UID	(0008,1155)

[Describe each supported custom Image Display Format (2010,0010) and provide details such as position and dimensions of each composing Image Box, including the numbering scheme of the image positions.]

[Describe each supported Annotation Display Format ID (2010,0030) (e.g., position and dimensions of annotation box, font, number of characters).]

[Describe supported configuration information (e.g., identification, content).]

N.5.2.8.7.3 Basic Grayscale Image Box SOP Class

Table N.5-45 lists the supported DIMSE Service for the Basic Grayscale Image Box SOP Class:

Table N.5-45. Services for the Basic Grayscale Image Box SOP Class- SCP

DIMSE Service Element	Purpose
N-SET	Set each Image Attributes for a previously created Film Box

Table N.5-46 lists the supported N-SET Attributes for Basic Grayscale Image Box:

[List the supported Attributes and their possible Values. Indicate the default Value when relevant. See example below.]

Table N.5-46. Supported N-SET Attributes for Basic Grayscale Image Box - SCP

Attribute name	Tag	Values	Default
Magnification Type	(2010,0060)	<<REPLICATE BILINEAR CUBIC NONE …>>	CUBIC
Smoothing Type	(2010,0080)	<possible Values or range>	143
Minimum Density	(2010,0120)	<possible Values or range in hundredths of OD>
Maximum Density	(2010,0130)	<possible Values or range in hundredths of OD>	320
Configuration Information	(2010,0150)
Image Box Position	(2020,0010)	<possible Position Values or range>
Polarity	(2020,0020)	<<NORMAL REVERSE>>	NORMAL
Requested Image Size	(2020,0030)	width, x-dimension, in mm
Requested Decimate/Crop Behavior	(2020,0040)	<<DECIMATE CROP FAIL>>
Basic Grayscale Image Sequence	(2020,0110)
>Samples per Pixel	(0028,0002)	1
>Photometric Interpretation	(0028,0004)	<<MONOCHROME1 MONOCHROME2>>
>Rows	(0028,0010)
>Columns	(0028,0011)
>Pixel Aspect Ratio	(0028,0034)		1\1
>Bits Allocated	(0028,0100)	<<8 16>>
>Bits Stored	(0028,0101)	<<8 12>>
>High Bit	(0028,0102)	<<7 11>>
>Pixel Representation	(0028,0103)	0	0
>Pixel Data	(7FE0,0010)
Referenced Presentation LUT Sequence	(2050,0500)
>Referenced SOP Class UID	(0008,1150)	1.2.840.10008.5.1.1.23
>Referenced SOP Instance UID	(0008,1155)

[If cropping or decimating of images is supported, describe the algorithm for removing rows and columns from the image.]

N.5.2.8.7.4 Printer SOP Class

Table N.5-47 lists the supported DIMSE Services for the Printer SOP Class:

Table N.5-47. Services for the Printer SOP Class - SCP

DIMSE Service Element	Purpose
N-EVENT-REPORT	Report the printer status in an asynchronous way
N-GET	Retrieve printer information and status.

Table N.5-48 lists the Printer SOP Class N-EVENT-REPORT Behavior:

Table N.5-48. Printer SOP Class N-EVENT-REPORT Behavior

Event Type Name	Event Type ID	Attribute Name	Tag	Values
Normal	1	N/A
Warning	2	Printer Status info	(2110,0020)	[Indicate the possible Values supported by the printer out of the defined terms table. See PS 3.3 Section C.13.9.1 for Defined Terms when the Printer Status is equal to WARNING or FAILURE]
		Film Destination	(2000,0040)
		Printer Name	(2110,0030)
Failure	3	Printer Status info	(2110,0020)	[Indicate the possible Values supported by the printer out of the defined terms table. See PS 3.3 Section C.13.9.1 for Defined Terms when the Printer Status is equal to WARNING or FAILURE]
		Film Destination	(2000,0040)
		Printer Name	(2110,0030)

Table N.5-49 lists the supported N-GET Attributes for Printer SOP Class:

[List the supported Attributes. Remove the non-supported Attributes from the Table]

Table N.5-49. Supported N-GET Attributes for the Printer SOP Class - SCP

Attribute Name	Tag	Values
Printer Status	(2110,0010)	<<NORMAL WARNING FAILURE>>
Printer Status Info	(2110,0020)	[Indicate the possible Values supported by the printer out of the defined terms table. See PS 3.3 Section C.13.9.1 for Defined Terms when the Printer Status is equal to WARNING or FAILURE]
Printer Name	(2110,0030)
Manufacturer	(0008,0070)
Manufacturer Model Name	(0008,1090)
Device Serial Number	(0018,1000)
Software Versions	(0018,1020)
Date Last Calibration	(0018,1200)
Time Last Calibration	(0018,1201)

N.5.2.8.8 SCP of the Basic Color Print Management Meta SOP Class

The Basic Color Print Management Meta SOP Class is composed of the mandatory SOP Classes listed in Table N.5-50:

Table N.5-50. Basic Color Print Management Meta OP Classes - SCP

SOP Class Name	SOP Class UID
Basic Film Session	1.2.840.10008.5.1.1.1
Basic Film Box	1.2.840.10008.5.1.1.2
Basic Color Image Box	1.2.840.10008.5.1.1.4.1
Printer	1.2.840.10008.5.1.1.16

N.5.2.8.8.1 Basic Film Session SOP Class

[If your system also supports the Basic Grayscale Print Management Meta SOP Class and the Film Session parameters are identical for color, see 'Basic Film Session SOP Class' for 'Basic Grayscale Print Management Meta SOP Class' in Section N.5.2.8.7.1. Otherwise copy the Film session table here and fill in the proper Values.]

N.5.2.8.8.2 Basic Film Box SOP Class

[If your system also supports the Basic Grayscale Print Management Meta SOP Class and the Film Box parameters are identical for color, see 'Basic Film Box SOP Class' for 'Basic Grayscale Print Management Meta SOP Class' in Section N.5.2.8.7.2. Otherwise copy the Film Box Table here and fill in the proper Values.]

N.5.2.8.8.3 Basic Color Image Box SOP Class

Table N.5-51 lists the supported DIMSE Service for the Basic Color Image Box SOP Class:

Table N.5-51. Services for the Basic Color Image Box SOP Class - SCP

DIMSE Service Element	Purpose
N-SET	Set each Image Attributes for a previously created Film Box

Table N.5-52 lists the supported N-SET Attributes for Basic Color Image Box:

[List the supported Attributes and their possible Values. Indicate the default Value when relevant. See example below.]

Table N.5-52. Supported N-SET Attributes for Basic Color Image Box - SCP

Attribute Name	Tag	Values	Default
Magnification Type	(2010,0060)	<<REPLICATE BILINEAR CUBIC NONE …>>	CUBIC
Smoothing Type	(2010,0080)	<possible Values or range>	143
Image Box Position	(2020,0010)	<possible Position Values or range>
Polarity	(2020,0020)	<<NORMAL REVERSE>>	NORMAL
Requested Image Size	(2020,0030)	width, x-dimension, in mm
Requested Decimate/Crop Behavior	(2020,0040)	<<DECIMATE CROP FAIL>>
Basic Color Image Sequence	(2020,0111)
>Samples per Pixel	(0028,0002)	3
>Photometric Interpretation	(0028,0004)	RGB
>Planar Configuration	(0028,0006)	1 (frame interleaves)
>Rows	(0028,0010)
>Columns	(0028,0011)
>Pixel Aspect Ratio	(0028,0034)		1\1
>Bits Allocated	(0028,0100)	8
>Bits Stored	(0028,0101)	8
>High Bit	(0028,0102)	7
>Pixel Representation	(0028,0103)	0
>Pixel Data	(7FE0,0010)

[In case your printer is a grayscale printer that supports printing of color images (e.g., it supports the Basic Color Print Management Meta SOP Class), describe the behavior when printing color images.]

N.5.2.8.8.4 Printer SOP Class

[If your system also supports the Basic Grayscale Print Management Meta SOP Class, see 'Printer SOP Class' for 'Basic Grayscale Print Management Meta SOP Class' in Section N.5.2.8.7.4. Otherwise copy the Printer SOP Class Table here and fill in the proper Values.]

N.5.2.8.9 SCP of the Basic Annotation Box SOP Class

Table N.5-53 lists the supported DIMSE Service for the Basic Annotation Box SOP Class:

Table N.5-53. Services for the Basic Annotation Box SOP Class - SCP

DIMSE Service Element	Purpose
N-SET	Set each Image Attributes for a previously created film box

Table N.5-54 lists the supported N-SET Attributes for Basic Annotation Box SOP Class:

[List the supported Attributes and their possible Values. Indicate the default Value when relevant. See example below.]

Table N.5-54. Supported N-SET Attributes for Basic Annotation Box SOP Class - SCP

Attribute Name	Tag	Values	Default
Annotation Position	(2030,0010)
Text String	(2030,0020)	Free text

N.5.2.8.10 SCP of the Print Job SOP Class

Table N.5-55 lists the supported DIMSE Services for the Print Job SOP Class:

Table N.5-55. Services for the Print Job SOP Class - SCP

DIMSE Service Element	Purpose
N-EVENT-REPORT	Report the printer status in an asynchronous way
N-GET	Retrieve printer information and status.

An N-EVENT-REPORT request can be sent by the SCP at any time during an Association if the print Job SOP Class has been negotiated by the SCU.

Table N.5-56 lists the supported Event Types and Attributes within the N-EVENT-REPORT.

Table N.5-56. Print Job SOP Class N-EVENT-REPORT- SCP

Event Type name	Event Type ID	Attribute Name	Tag	Values
Pending	1	Execution Status Info	(2100,0030)	[Indicate the possible Values supported by the printer out of the Defined Terms Table. See PS 3.3 Section C.13.9.1 for Defined Terms when the Execution Status info is PENDING or FAILURE]
		Film Session Label	(2000,0050)
		Printer Name	(2110,0030)
Printing	2	Execution Status Info	(2100,0030)	NORMAL
		Film Session Label	(2000,0050)
		Printer Name	(2110,0030)
Done	3	Execution Status Info	(2100,0030)	NORMAL
		Film Session Label	(2000,0050)
		Printer Name	(2110,0030)
Failure	4	Execution Status Info	(2100,0030)	[Indicate the possible Values supported by the printer out of the Defined Terms Table See PS 3.3 Section C.13.9.1 for Defined Terms when the Execution Status info is PENDING or FAILURE]
		Film Session Label	(2000,0050)
		Printer Name	(2110,0030)

[Remove the complete table if N-GET is not supported.]

Table N.5-57 lists the supported N-GET Attributes for Print Job SOP Class:

[List the supported Attributes and the supported Values when relevant. Remove the non-supported Attributes from the table.]

Table N.5-57. Supported N-GET Attributes for the Print Job SOP Class - SCP

Attribute Name	Tag	Values
Print Priority	(2000,0020)	<<HIGH MEDIUM LOW>>
Execution Status	(2100,0020)	<<PENDING PRINTING DONE FAILURE>>
Execution Status Info	(2100,0030)	[Indicate the possible Values supported by the printer out of the Defined Terms Table. See PS3.3 Section C.13.9.1 for Defined Terms when the Execution Status info is PENDING or FAILURE]
Creation Date	(2100,0040)
Creation Time	(2100,0050)
Originator	(2100,0070)
Printer Name	(2110,0030)

N.5.2.8.11 SCP of the Presentation LUT SOP Class

Table N.5-58 lists the supported DIMSE Services for the Presentation LUT SOP Class:

Table N.5-58. Services for the Presentation LUT SOP Class SCP

DIMSE Service Element	Purpose
N-CREATE	Create the Presentation LUT Instance
N-DELETE	Delete the Presentation LUT Instance

Table N.5-59 lists the supported N-CREATE Attributes for Presentation LUT:

[List the supported Attributes in Table N.5-59.]

Table N.5-59. Supported N-CREATE Attributes for Presentation LUT - SCP

Attribute Name	Tag	Values
Presentation LUT Sequence	(2050,0010)
>LUT Descriptor	(0028,3002)
>LUT Explanation	(0028,3003)
>LUT Data	(0028,3006)
Presentation LUT Shape	(2050,0020)	<<IDENTITY LIN OD>>

N.5.2.8.12 SCP of the Printer Configuration Retrieval SOP Class

Table N.5-60 lists the supported DIMSE Services for the Printer Configuration Retrieval SOP Class:

Table N.5-60. Services for the Printer Configuration Retrieval SOP Class

DIMSE Service Element	Purpose
N-GET	Retrieve printer configuration.

N.5.3 DICOM Web Services

N.5.3.1 URI Web Service (WADO URI)

This section provides details regarding the URI Web Service. For an overview of the supported transactions see Table N.1-8 URI Service.

N.5.3.1.1 Supported Web Media Types

N.5.3.1.1.1 DICOM Media Types

The supported DICOM Storage SOP Classes / Transfer Syntaxes are listed in Section N.1.1 of this document.

[Provide requirements for display and processing of instances received via Web Services. This could either be done by referencing Section N.5.2.5.2 if the same requirements apply, or by copying the tables from Section N.5.2.5.2 and filling them appropriately, if the requirements for Web Services differ.]

N.5.3.1.1.2 Rendered Media Types

Table N.5-61 lists the supported rendered Media types depending on the Media Type category.

[Indicate which category / Media types are supported by your system by marking the cells with Y or N. Remove rows for Media Types neither supported as user agent nor as Origin Server].

Table N.5-61. Supported Rendered Media Types

Category	Media Type	URI User Agent	URI Origin Server
Single Frame Image	image/jpeg
	image/gif
	image/png
	image/jp2
	image/jph
	image/jxl
Multi-Frame Image	image/gif
Multi-Frame Image	image/jxl
Video	video/mpeg
	video/mp4
	video/H265
Text	text/html
	text/plain
	text/xml
	text/rtf
	application/pdf

N.5.3.1.2 Retrieve DICOM Instance Transaction - URI Web Service

[Provide requirements for display and processing of instances retrieved via URI Web Service. This could either be done by referencing Section N.5.2.5.2 (as indicated below), if the same requirements apply, or by copying the tables from Section N.5.2.5.2 and filling them appropriately if requirements for retrieved instances differ.]

In order to display or process DICOM instances retrieved via URI Web Service, see Section N.5.2.5.2.

N.5.3.1.2.1 User Agent

The URI Web Service user agent supports the Query Parameters listed in Table N.5-62.

[List the supported parameters and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-62. Query Parameters for Retrieve DICOM Instance URI Web Service - User Agent

Query Parameter	Supported Values	Comments
requestType	WADO
studyUID	<Study Instance UID>
seriesUID	<Series Instance UID>
objectUID	<SOP Instance UID>
contentType	application/dicom	[Must be compatible with the acceptable Media Types in the HTTP Header] See in the Overview section Table N.1-1 the supported DICOM SOP Classes / Transfer Syntaxes. Look for "Y" in the "UA" column
charset	<<UTF-8 ISO-8859-1 …>>
anonymize	yes
transferSyntax

The URI Web Service User Agent supports the Header Fields listed in Table N.5-63:

[List the supported Header Fields and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-63. Header Fields for Retrieve DICOM Instance URI Web Service - User Agent

Header Field

Supported Values

Comments

application/dicom

See in the Overview section Table N.1-1 the supported DICOM SOP Classes / Transfer Syntaxes. Look for "Y" in the "UA" column

Accept-charset

<<UTF-8

ISO-8859-1

…>>

N.5.3.1.2.2 Origin Server

The URI Web Service origin server receives GET requests for studies, series and instances containing query parameters and headers fields. Supported Values are listed in the query parameters and header fields tables (Table N.5-64 and Table N.5-65).

The URI is composed by a Base URI: see Section N.6.3.1 for the Base URI of the Origin Server.

The URI Web Service origin server supports the Query Parameters listed in Table N.5-64.

[List the supported parameters and their Values. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-64. Query Parameters for Retrieve DICOM Instance URI Web Service - Origin Server

Query Parameter	Supported Values	Comments
requestType	WADO
studyUID	<Study Instance UID>
seriesUID	<Series Instance UID>
objectUID	<SOP Instance ID>
contentType	application/dicom	See in the Overview section Table N.1-1 the supported DICOM SOP Classes / Transfer Syntaxes. Look for "Y" in the "OS" column
charset	<<UTF-8 ISO-8859-1 …>>
anonymize
transferSyntax

The URI Web Service origin server supports the Header Fields listed in Table N.5-65.

[List the supported Header Fields and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-65. Header Fields for Retrieve DICOM Instance URI Web Service - Origin Server

Header Field

Supported Values

Comments

application/dicom

See in the Overview section Table N.1-1 the supported DICOM SOP Classes / Transfer Syntaxes. Look for "Y" in the "OS" column

Accept-charset

<<UTF-8

ISO-8859-1

…>>

N.5.3.1.3 Retrieve Rendered Instance Transaction - URI Web Service

[Provide requirements for display and processing of instances retrieved via URI Web Service. This could either be done by referencing section 5.2.5.2 (as indicated below), if the same requirements apply, or by copying the tables from Section 5.2.5.2 and filling them appropriately if requirements for retrieved instances differ.]

To display or process DICOM instances retrieved via URI Web Service, see Section N.5.2.5.2.

N.5.3.1.3.1 User Agent

The URI Web Service user agent supports the Query Parameters listed in Table N.5-66.

[List the supported parameters and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-66. Query Parameters for Retrieve Rendered Instance URI Web Service - User Agent

Query Parameter	Supported Values	Comments
requestType	WADO
studyUID	<Study Instance UID>
seriesUID	<Series Instance UID>
objectUID	<SOP Instance UID>
contentType	<<image/jpeg image/gif image/png image/jp2 video/mpeg video/mp4 video/H265 text/html text/plain>>	See Section N.5.3.1.1.2 for details
charset	<<UTF-8 ISO-8859-1 …>>
annotation
rows
columns
region
windowCenter
windowWidth
frameNumber
imageQuality		[The Value must be between 1 and 100. 1 means low quality and 100 imeans high quality]
presentationUID and presentationSeriesUID		[if presentationUID specified then presentationSeriesUID must be present.]

The URI Web Service user agent supports Header Fields listed in Table N.5-67.

[List the supported Header Fields and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-67. Header Fields for Retrieve Rendered Instance URI Web Service - User Agent

Header Field

Supported Values

Comments

<<image/jpeg

image/gif

image/png

image/jp2

video/mpeg

video/mp4

video/H265

text/html

text/plain>>

See Section N.5.3.1.1.2 for details

Accept-charset

<<UTF-8

ISO-8859-1

…>>

N.5.3.1.3.2 Origin Server

The URI is composed by a Base URI: see Section N.6.3.1 for the Base URI of the origin server.

The URI Web Service origin server supports Query Parameters listed in Table N.5-68.

[List the supported parameters and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-68. Query Parameters for Retrieve Rendered Instance URI Web Service - Origin Server

Query Parameter	Supported Values	Comments
requestType	WADO
studyUID	<Study Instance UID>
seriesUID	<Series Instance UID>
objectUID	<SOP Instance ID>
contentType	<<image/jpeg image/gif imag/png image/jp2 video/mpeg video/mp4 video/H265 text/html text/plain >>	See details in Section N.5.3.1.1.2
charset	<<UTF-8 ISO-8859-1 …>>
annotation	<<patient technique>> Add additionally supported key word Values here
rows
columns
region
windowCenter
windowWidth
frameNumber
imageQuality		[The Value must be between 1 and 100. 1 means low quality and 100 imeans high quality.]
presentationUID and presentationSeriesUID		[if presentationUID specified then presentationSeriesUID must be present.]

The URI Web Service origin server supports Header Fields listed in Table N.5-69.

[List the supported Header Fields and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-69. Header Fields for Retrieve Rendered Instance URI Web Service - Origin Server

Header Field

Supported Values

Comments

<<Image/jpeg

image/gif

image/png

image/jp2

video/mpeg

video/mp4

video/H265

text/html

text/plain>>

See details in Section N.5.3.1.1.2 Rendered Media Types

N.5.3.2 Studies Web Service

This section provides details regarding the Studies Web Service. For an overview of supported transactions and resources see Table N.1-9 Study Service.

N.5.3.2.1 Supported Web Media Types

N.5.3.2.1.1 DICOM Media Types

The supported DICOM Storage SOP Classes / Transfer Syntaxes are listed in Section N.1.1 of this document.

N.5.3.2.1.2 DICOM Bulkdata Media Type

[Indicate in the Table the combination media type / Transfer Syntaxes supported by your user agent and / or origin server for each category. Remove the unsupported Media Types.X represents the default Transfer Syntaxes to be supported for each category.]

Uncompressed Bulkdata is transferred using Explicit VR Little Endian Transfer Syntax.

Table N.5-70 lists the supported Media Types and Transfer Syntax UIDs for Compressed Bulkdata.

Table N.5-70. DICOM Compressed Bulkdata Media Types

Category	Media Type	Transfer Syntax UID	Transfer Syntax Name
Single Frame Image	image/jpeg	1.2.840.10008.1.2.4.70	JPEG Lossless, Non-Hierarchical, First-Order Prediction(Process 14 Selection Value 1): Default Transfer Syntax for Lossless JPEG Image Compression
		1.2.840.10008.1.2.4.50	JPEG Baseline (Process 1): Default Transfer Syntax for Lossy JPEG 8 Bit Image Compression
		1.2.840.10008.1.2.4.51	JPEG Extended (Process 2 & 4): Default Transfer Syntax for Lossy JPEG 12 Bit Image Compression (Process 4 only)
		1.2.840.10008.1.2.4.57	JPEG Lossless, Non-Hierarchical (Process 14)
	image/x-dicom-rle	1.2.840.10008.1.2.5	RLE Lossless
	image/x-jls	1.2.840.10008.1.2.4.80	JPEG-LS Lossless Image Compression
	image/x-jls	1.2.840.10008.1.2.4.81	JPEG-LS Lossy (Near-Lossless) Image Compression
	image/jp2	1.2.840.10008.1.2.4.90	JPEG 2000 Image Compression (Lossless Only)
	image/jp2	1.2.840.10008.1.2.4.91	JPEG 2000 Image Compression
	image/jpx	1.2.840.10008.1.2.4.92	JPEG 2000 Part 2 Multi-component Image Compression (Lossless Only)
	image/jpx	1.2.840.10008.1.2.4.93	JPEG 2000 Part 2 Multi-component Image Compression
	image/jphc	1.2.840.10008.1.2.4.201	High-Throughput JPEG 2000 Image Compression (Lossless Only)
		1.2.840.10008.1.2.4.202	High-Throughput JPEG 2000 with RPCL Options Image Compression (Lossless Only)
		1.2.840.10008.1.2.4.203	High-Throughput JPEG 2000 Image Compression
	image/jxl	1.2.840.10008.1.2.4.110	JPEG XL Lossless
		1.2.840.10008.1.2.4.111	JPEG XL
		1.2.840.10008.1.2.4.112	JPEG XL JPEG Recompression
Multi-frame Image	image/jpeg	1.2.840.10008.1.2.4.70	JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14 Selection Value 1): Default Transfer Syntax for Lossless JPEG Image Compression
		1.2.840.10008.1.2.4.50	JPEG Baseline (Process 1): Default Transfer Syntax for Lossy JPEG 8 Bit Image Compression
		1.2.840.10008.1.2.4.51	JPEG Extended (Process 2 & 4): Default Transfer Syntax for Lossy JPEG 12 Bit Image Compression (Process 4 only)
		1.2.840.10008.1.2.4.57	JPEG Lossless, Non-Hierarchical (Process 14)
	image/x-dicom-rle	1.2.840.10008.1.2.5	RLE Lossless
	image/x-jls	1.2.840.10008.1.2.4.80	JPEG-LS Lossless Image Compression
	image/x-jls	1.2.840.10008.1.2.4.81	JPEG-LS Lossy (Near-Lossless) Image Compression
	image/jp2	1.2.840.10008.1.2.4.90	JPEG 2000 Image Compression (Lossless Only)
	image/jp2	1.2.840.10008.1.2.4.91	JPEG 2000 Image Compression
	image/jpx	1.2.840.10008.1.2.4.92	JPEG 2000 Part 2 Multi-component Image Compression (Lossless Only)
	image/jpx	1.2.840.10008.1.2.4.93	JPEG 2000 Part 2 Multi-component Image Compression
	image/jphc	1.2.840.10008.1.2.4.201	High-Throughput JPEG 2000 Image Compression (Lossless Only)
		1.2.840.10008.1.2.4.202	High-Throughput JPEG 2000 with RPCL Options Image Compression (Lossless Only)
		1.2.840.10008.1.2.4.203	High-Throughput JPEG 2000 Image Compression
	image/jxl	1.2.840.10008.1.2.4.110	JPEG XL Lossless
		1.2.840.10008.1.2.4.111	JPEG XL
		1.2.840.10008.1.2.4.112	JPEG XL JPEG Recompression
Video	video/mpeg2	1.2.840.10008.1.2.4.100	MPEG2 Main Profile @ Main Level
	video/mpeg2	1.2.840.10008.1.2.4.101	MPEG2 Main Profile @ High Level
	video/mp4	1.2.840.10008.1.2.4.102	MPEG-4 AVC/H.264 High Profile / Level 4.1
		1.2.840.10008.1.2.4.103	MPEG-4 AVC/H.264 BD-compatible High Profile / Level 4.1
		1.2.840.10008.1.2.4.104	MPEG-4 AVC/H.264 High Profile / Level 4.2 For 2D Video
		1.2.840.10008.1.2.4.105	MPEG-4 AVC/H.264 High Profile / Level 4.2 For 3D Video
		1.2.840.10008.1.2.4.106	MPEG-4 AVC/H.264 Stereo High Profile / Level 4.2

N.5.3.2.1.3 Supported Rendered Media Types

Table N.5-71 lists the supported Rendered Media types for each Media Type category.

[Indicate which category / Media types are supported by your system by marking the cells with Y or N. Remove rows for Media Types neither supported as user agent nor as origin server.

In the Transformation column specify to which Transfer Syntax UID the origin server transforms the received image. N/A indicates that the media type does not require transformation since there is an existing DICOM Transfer Syntax for it.]

Table N.5-71. Rendered Media Types

Category	Media Type	User Agent	Origin Server	Transformation
Single Frame Image	image/jpeg
	image/gif
	image/png
	image/jp2
	image/jph
	image/jxl
Multi-Frame Image	image/gif
Multi-Frame Image	image/jxl
Video	video/mpeg
	video/mp4
	video/H265
Text	text/html
	text/plain
	text/xml
	text/rtf
	application/pdf

N.5.3.2.2 Retrieve supported transaction (WADO-RS)

The Studies Web Service Retrieve Transaction is also known as WADO-RS.

N.5.3.2.2.1 User Agent

The Retrieve Transaction user agent can request resources listed in Table N.5-72:

[List the supported resources for your Retrieve Transaction user agent. Remove the non-supported resources rows. Fill in specific details on your implementation in the in the "Comments" column, when necessary.]

Table N.5-72. Resources Retrieve Transaction - User Agent

Resource	Comments
DICOM Instance Resources - See Resources path in Table 10.4.1-1 in PS3.18
Study Instances
Series Instances
Individual Instance
DICOM Metadata Resources - See Resources path in Table 10.4.1-2 in PS3.18
Study Metadata
Series Metadata
Instance Metadata
DICOM Bulkdata Resources - See Resources path in Table 10.4.1.5-1 in PS3.18
Study Bulkdata
Series Bulkdata
Instance Bulkdata
Bulkdata
DICOM Pixel Data Resources - See Resources path in Table 10.4.1.6-1 in PS3.18
Study Pixel Data
Series Pixel Data
Instance Pixel Data
Frame Pixel Data
Rendered Resources - See Resources path in Table 10.4.1-3 in PS3.18
Rendered Study
Rendered Series
Rendered Instance
Rendered Frame
Rendered MPR Volume Resources - See Resources path in Table 10.4.1.7-1 in PS3.18
Rendered MPR Volume Study
Rendered MPR Volume Series
Rendered MPR Volume Instance
Rendered MPR Volume Frames
Rendered 3D Volume Resources - See Resources path in Table 10.4.1.8-1 in PS3.18
Rendered 3D Volume Study
Rendered 3D Volume Series
Rendered 3D Volume Instance
Rendered 3D Volume Frames
Thumbnail Resources - See Resources path in Table 10.4.1-4 in PS3.18
Study Thumbnail
Series Thumbnail
Instance Thumbnail
Frame Thumbnail

[If rendering of thumbnails is supported, provide a high-level description of the method used for rendering thumbnails for the study, series, or instance.

For example, the description could indicate whether a representative instance is chosen from a series, and how that instance is selected, or that per-modality fixed content is used.]

The Retrieve Transaction user agent supports the Query Parameters listed in Table N.5-73.

[Include a row in the table for each parameter your user agent is able to send, including parameters always sent and parameters optionally sent. Remove the rows for parameters your user agent is not able to send. See Section 8.3.5 in PS3.18 for the list of Rendering Query Parameters.

For each row, indicate in the Supported Values column specific Values your user agent may send and/or a description of how the Value is populated. The "Comments" column may be used to explain details of your implementation that may be useful to integrators, such as:

Whether and how Values are configurable
Situations when the parameter may or may not be sent, or when specific Values may be used
How the Accept Query Parameter is intended to relate to the Accept Header Field
Other idiosyncrasies of the implementation

]

Table N.5-73. Query Parameters for Retrieve Transaction - User Agent

Query Parameter	Supported Values	Comments
Accept	[See examples in header parameters.]
Rendered Resource
annotation	<<patient technique>>
charset	<<UTF-8 ISO-8859-1 …>>
quality
viewport
window
iccprofile	<<no yes srgb adobergb rommrgb>>
Rendered MPR Volume Resources
volumeinputreference
match	Attribute Values to address the search (matching key). See the supported DICOM Attribute in the Table N.5-84
renderingmethod	<<volume_rendered maximum_ip minimum_ip average_ip>>
orientation
viewpointposition
viewpointlookat
viewpointup
mprslab
volumetriccurvepoint
animationstepsize
animationrate
renderedvolumetricmetadata
Rendered 3D Volume Resources
volumeinputreference
match	Attribute Values to address the search (matching key). See the supported DICOM Attribute in the Table N.5-84
renderingmethod	<<volume_rendered maximum_ip minimum_ip average_ip>>
orientation
viewpointposition
viewpointlookat
viewpointup
swivelrange
animationstepsize
animationrate
renderedvolumetricmetadata
Thumbnail Resource
charset	<<UTF-8 ISO-8859-1 …>>
viewport

The Retrieve Transaction user agent supports Header Fields listed in Table N.5-74.

[List the supported Header Fields and their supported Values. Fill in information on your implementation in the "Comments" column when necessary. See Section 10.4.4 in PS3.18 for the list of resources and their corresponding Media Types.]

Table N.5-74. Header Fields for Retrieve Transaction - User Agent

Header Field	Supported Values	Comments
Instance resource
Accept	multipart/related; type="application/dicom"; transfer-syntax={uid}	See in the Overview section Table N.1-1 the supported DICOM SOP Classes / Transfer Syntaxes. Look for "Y" in the "UA" column.
Accept	multipart/related; type="application/octet-stream"
Metadata resource
Accept	<<multipart/related; type="application/dicom+xml" multipart/related; type="application/dicom+json">>
Bulkdata and Pixel Data resource
Accept	Uncompressed: <<multipart/related; type="application/octet-stream">> Compressed: <<multipart/related; type="{media-type}">> supported {media-type} being <<image/jpeg image/x-dicom-rle image/x-jls image/jp2 image/jphc image/jpx image/jxl video/mpeg2 video/mp4>>	See details in Section N.5.3.2.1.2.
Rendered Resource
Accept	<<image/jpeg image/gif image/png image/jp2 image/jph image/jxl video/mpeg video/mp4 video/H265 text/html text/plain text/xml>>	See details in Section N.5.3.2.1.3.
Rendered MPR Volume Resources
Accept	<<image/jpeg image/gif image/png image/jp2 image/jph image/jphc image/jxl video/mpeg video/mp4 video/H265 multipart/related; type="application/dicom+xml" multipart/related; type="application/dicom+json">>	See details in Section N.5.3.2.1.3.
Rendered 3D Volume Resources
Accept	<<image/jpeg image/gif image/png image/jp2 image/jph image/jphc image/jxl video/mpeg video/mp4 video/H265 multipart/related; type="application/dicom+xml" multipart/related; type="application/dicom+json">>	See details in Section N.5.3.2.1.3.
Thumbnail Resource
Accept	<<image/jpeg image/gif image/png image/jp2 image/jph image/jxl video/mpeg video/mp4 video/H265 text/html text/plain text/xml>>	See details in Section N.5.3.2.1.3.
All Resources
Accept-charset	<<UTF-8 ISO-8859-1 …>>

N.5.3.2.2.2 Origin Server

The Retrieve Transaction origin server receives GET requests to retrieve specific studies, series or instances.

The user agent specifies the Target Resource as part of the URI and the acceptable response Content-Type in the HTTP Header (i.e., dicom, dicom+xml, dicom+json, octet-stream, compressed pixel data).

The URI is composed by a Base URI: see Section N.6.3.2.1 for the Base URI of the origin server

The Retrieve Transaction origin server supports resources listed in Table N.5-75.

[List the supported resources for your Retrieve Transaction origin server. Remove the non-supported resources rows.Fill in information on your implementation in the Comments column when necessary.]

Table N.5-75. Resources Retrieve Transaction - Origin Server

Resource	Comments
DICOM Instance Resources - See Resources path in Table 10.4.1-1 in PS3.18
Study Instances
Series Instances
Individual Instance
DICOM Metadata Resources - See Resources path in Table 10.4.1-2 in PS3.18
Study Metadata
Series Metadata
Instance Metadata
DICOM Bulkdata Resources - See Resources path in Table 10.4.1.5-1 in PS3.18
Study Bulkdata
Series Bulkdata
Instance Bulkdata
Bulkdata
DICOM Pixel Data Resources - See Resources path in Table 10.4.1.6-1 in PS3.18
Study Pixel Data
Series Pixel Data
Instance Pixel Data
Frame Pixel Data
Rendered Resources - See Resources path in Table 10.4.1-3 in PS3.18
Rendered Study
Rendered Series
Rendered Instance
Rendered Frame
Rendered MPR Volume Resources - See Resources path in Table 10.4.1.7-1 in PS3.18
Rendered MPR Volume Study
Rendered MPR Volume Series
Rendered MPR Volume Instance
Rendered MPR Volume Frames
Rendered MPR Volume Resources - See Resources path in Table 10.4.1.7-1 in PS3.18
Rendered 3D Volume Study
Rendered 3D Volume Series
Rendered 3D Volume Instance
Rendered 3D Volume Frames
Thumbnail Resources - See Resources path in Table 10.4.1-4 in PS3.18
Study Thumbnail
Series Thumbnail
Instance Thumbnail
Frame Thumbnail

Table N.5-76 lists Query parameters supported for the Retrieve Transaction as an origin server.

[List the supported parameters and their supported Values. Fill in information on your implementation in the "Comments" column when necessary. See Section 8.3.5 in PS3.18 for the list of Rendering Query Parameters.]

Table N.5-76. Query Parameters for Retrieve Transaction - Origin Server

Query Parameter	Supported Values	Comments
Accept	[Supported Values are the same as for the Accept Header Field.]
Rendered Resource
annotation	<<patient technique>> [Add additionally supported key word Values here.]
charset	<<UTF-8 ISO-8859-1 …>>
quality
viewport
window
iccprofile	<<no yes srgb adobergb rommrgb>>
Rendered MPR Volume Resources
volumeinputreference
match	Attribute Values to address the search (matching key). See the supported DICOM Attribute in the Table N.5-84
renderingmethod	<<volume_rendered maximum_ip minimum_ip average_ip>>
orientation
viewpointposition
viewpointlookat
viewpointup
mprslab
volumetriccurvepoint
animationstepsize
animationrate
renderedvolumetricmetadata
Rendered 3D Volume Resources
volumeinputreference
match	Attribute Values to address the search (matching key). See the supported DICOM Attribute in the Table N.5-84
renderingmethod	<<volume_rendered maximum_ip minimum_ip average_ip>>
orientation
viewpointposition
viewpointlookat
viewpointup
swivelrange
animationstepsize
animationrate
renderedvolumetricmetadata
Thumbnail Resource
charset	<<UTF-8 ISO-8859-1 …>>
viewport

The Retrieve Transaction origin server supports Header Fields listed in Table N.5-77.

[List the supported Header Field and their supported Values. Fill in information on your implementation in the "Comments" column when necessary. See Section 10.4.4 in PS3.18 for the list of resources and their corresponding Media Types.]

Table N.5-77. Header Fields for Retrieve Transaction - Origin Server

Header Field	Supported Values	Comments
Instance resource
Accept	multipart/related; type="application/dicom"; transfer-syntax={uid}	See in the Overview section Table N.1-1 the supported DICOM SOP Classes / Transfer Syntaxes. Look for "Y" in the "OS" column.
Accept	multipart/related; type="application/octet-stream"
Metadata resource
Accept	<<multipart/related; type="application/dicom+xml" multipart/related; type="application/dicom+json">>
Bulkdata and Pixel Data resource
Accept	Uncompressed: <<multipart/related; type="application/octet-stream">> Compressed: <<multipart/related; type="{media-type}">> supported {media-type} being <<Image/jpeg image/x-dicom-rle image/x-jls image/jp2 image/jphc image/jpx image/jxl video/mpeg2 video/mp4>>	See details in Section N.5.3.2.1.2.
Rendered Resource
Accept	<<image/jpeg image/gif image/png image/jp2 image/jph image/jxl image/gif video/mpeg video/mp4 video/H265 text/html text/plain text/xml>>	See details in Section N.5.3.2.1.3.
Rendered MPR Volume Resources
Accept	<<image/jpeg image/gif image/png image/jp2 image/jph image/jphc image/jxl video/mpeg video/mp4 video/H265 multipart/related; type="application/dicom+xml" multipart/related; type="application/dicom+json">>	See details in Section N.5.3.2.1.3.
Rendered 3D Volume Resources
Accept	<<image/jpeg image/gif image/png image/jp2 image/jph image/jphc image/jxl video/mpeg video/mp4 video/H265 multipart/related; type="application/dicom+xml" multipart/related; type="application/dicom+json">>	See details in Section N.5.3.2.1.3.
Thumbnail Resource
Accept	<<image/jpeg image/gif image/png image/jp2 image/jph image/jxl image/gif video/mpeg video/mp4 video/H265 text/html text/plain text/xml>>	See details in Section N.5.3.2.1.3.
All Resources
Content-Type	Content-Type returned by the origin server in the response. It contains the media type of the Payload. See Accept for supported Values
Content-Type	Accept-charset	<<UTF-8 ISO-8859-1 …>>

N.5.3.2.3 Store Transaction (STOW-RS)

N.5.3.2.3.1 User Agent

For details regarding the IODs created by the system, see Section N.9.

The Store Transaction user agent can request resources listed in Table N.5-78.

[List the supported resources for your Store Transaction user agent. Remove the non-supported resources rows.Fill in information on your implementation in the Comments column when necessary.]

Table N.5-78. Resources Store Transaction - User Agent

Resource	Comments
	See resource path in Table 10.5.1-1 in PS3.18
All Studies
Study

The Store Transaction user agent supports Header Fields listed in Table N.5-79.

[List the supported Header Fields and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-79. Header Fields for Store Transaction - User Agent

Header Field	Supported Values	Comments
Content-Type	multipart/related; type="application/dicom"; transfer-syntax={uid}	See in the Overview section Table N.1-1 the supported DICOM SOP Classes / Transfer syntaxes (look for "Y" in the "UA" column)
	multipart/related; type="application/dicom+xml"; boundary={messageBoundary} multipart/related; type="application/dicom+json"; boundary={messageBoundary}
	Uncompressed: multipart/related; type="application/octet-stream" Compressed: multipart/related; type="{media-type}" supported {media-type} being <<Image/jpeg image/x-dicom-rle image/x-jls image/jp2 image/jphc image/jpx image/jxl video/mpeg2 video/mp4>>	See details in Section N.5.3.2.1.2.
Content-Length		[If Content-Encoding is not present]
Content-Encoding		[If Content-Length is not present]

N.5.3.2.3.2 Origin Server

The Store Transaction origin server receives POST requests to store or append to an existing resource on the server.

The user agent specifies the Target Resource as part of the URI and encapsulates the data in a multipart request body with a proper Content-Type (i.e., BINARY, XML or JSON).

The URI is composed by a Base URI: see Base URI for the origin server in Section N.6.3.2.2.

The Store Transaction origin server can request resources listed in Table N.5-80.

[Fill in information on your implementation in the Comments column when necessary.]

Table N.5-80. Resources Store Transaction - Origin Server

Resource	Comments
	See resource path in Table 10.5.1-1 in PS3.18
All Studies
Study

The Store Transaction origin server supports Header Fields listed in Table N.5-81.

[List the supported Header Fields and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-81. Header Fields for Store Transaction - Origin Server

Header Field	Supported Values	Comments
Content-Type	multipart/related; type="application/dicom"; boundary={messageBoundary} multipart/related; type="application/dicom+xml"; boundary={messageBoundary} multipart/related; type="application/dicom+json"; boundary={messageBoundary} multipart/related; type="application/octet-stream"	See in the Overview section Table N.1-1 the supported DICOM SOP Classes / Transfer syntaxes (look for "Y" in the "OS" column)
	multipart/related; type="application/dicom+xml"; boundary={messageBoundary} multipart/related; type="application/dicom+json"; boundary={messageBoundary}
	Uncompressed: multipart/related; type="application/octet-stream" Compressed: multipart/related; type="{media-type}" supported {media-type} being <<Image/jpeg image/x-dicom-rle image/x-jls image/jp2 image/jpx image/jphc image/jxl video/mpeg2 video/mp4>>	See details in Section N.5.3.2.1.2.
Content-Length		[If Content-Encoding is not present.]
Content-Encoding		[If Content-Length is not present.]

N.5.3.2.4 Search Transaction (QIDO-RS)

N.5.3.2.4.1 User Agent

The Search Transaction user agent can request resources listed in Table N.5-82.

[List the supported resources for your Search Transaction user agent. Remove the non-supported resources rows. Fill in specific details of your implementation if available in the "Comments" column.]

Table N.5-82. Resources Search Transaction - User Agent

Resource	Comments
	See resource path in Table 10.6.1-1 in PS3.18
All studies
All series
All instances
Study's Series
Study's instances
Study Series's Instances

The Search Transaction user agent supports query parameters listed in Table N.5-83.

[Indicate the supported parameters and their supported Values. For detail on the implementation possibilities see Table 8.3.4-1 in PS3.18. Fill in specific details of your implementation if available in the "Comments" column.]

Table N.5-83. Query Parameters for Search Transaction - User Agent

Query Parameter	Supported Values	Comments
match	Attribute Values to address the search (matching key). See the supported DICOM Attribute in the Table N.5-84
includefield	Attributes to be included in the response (return key). See the supported DICOM Attributes in the Table N.5-84
fuzzymatching	<<true false>>
emptyvaluematching	<<true false>>
multiplevaluematching	<<true false>>
Limit		[Maximum number of results the server returns.]
Offset		[Number of results the server skips before the first returned result.]

[Indicate which DICOM query Attributes are supported and if they are supported as Matching and/or Return (include) key. Add or remove Attributes according to your implementation. If the tables are the same as used in DIMSE Services, you can enter a reference to Table N.5-17 and remove the text and table below. Otherwise provide the following text and Table N.5-84.]

Table N.5-84 lists the DICOM query Attributes supported by the Search Transaction user agent.

Table N.5-84. Supported Query Attributes User Agent

Attribute Name	Tag	Matching Key	Return Key	Comments
Study Level (May be used for All studies, All series, All instance resource query)
SpecificCharacterSet	(0008,0005)
StudyDate	(0008,0020)
StudyTime	(0008,0030)
AccessionNumber	(0008,0050)
ModalitiesInStudy	(0008,0061)
ReferringPhysicianName	(0008,0090)
TimezoneOffsetFromUTC	(0008,0201)
PatientName	(0010,0010)
PatientID	(0010,0020)
PatientBirthDate	(0010,0030)
PatientSex	(0010,0040)
StudyInstanceUID	(0020,000D)
StudyID	(0020,0010)
NumberOfStudyRelatedSeries	(0020,1206)
NumberOfStudyRelatedInstances	(0020,1208)
…
Series Level (May be used for All Series, Study's Series, Study's Instances, All Instances resource query)
SpecificCharacterSet	(0008,0005)
Modality	(0008,0060)
TimezoneOffsetFromUTC	(0008,0201)
SeriesDescription	(0008,103E)
SeriesInstanceUID	(0020,000E)
SeriesNumber	(0020,0011)
NumberOfSeriesRelatedInstances	(0020,1209)
PerformedProcedureStepStartDate	(0040,0244)
PerformedProcedureStepStartTime	(0040,0245)
RequestAttributeSequence	(0040,0275)
> RequestedProcedureID	(0040,1001)
> ScheduledProcedureStepID	(0040,0009)
…
Instance Level (May be used for All instances, Study's instance, Study Series's instance resource query)
SpecificCharacterSet	(0008,0005)
SOPClassUID	(0008,0016)
SOPInstanceUID	(0008,0018)
InstanceAvailability	(0008,0056)
TimezoneOffsetFromUTC	(0008,0201)
RetrieveURL	(0008,1190)
InstanceNumber	(0020,0013)
Rows	(0028,0010)
Columns	(0028,0011)
BitsAllocated	(0028,0100)
NumberOfFrames	(0028,0008)
…

The Search Transaction user agent supports Header Fields listed in Table N.5-85.

[List the supported Header Fields and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-85. Header Fields for Search Transaction - User Agent

Header Field

Supported Values

Comments

<<multipart/related; type="application/dicom+xml"

application/dicom+json>>

Accept-charset

See Section N.5.7 for supported Values

N.5.3.2.4.2 Origin Server

The Search Transaction origin server receives GET requests to search for studies, series or instances.

[Specify here if this is a native or a DIMSE proxy implementation.]

The user agent specifies the Target Resource as part of the URI and the acceptable response Content-Type in the HTTP Header (i.e., dicom+xml or dicom+json).

The URI is composed by a Base URI: see Base URI for the origin server in Section A.6.3.2.3.

The Search Transaction origin server supports resources listed in Table N.5-86.

[Fill in information on your implementation in the Comments column when necessary.]

Table N.5-86. Resources Search Transaction - Origin Server

Transaction	Resource	Comments
		See resource path in Table 10.6.1-1 in PS3.18
Search	All Studies
	All Series
	All Instances
	Study's Series
	Study's Instances
	Study Series' Instances

The Search Transaction origin server supports query parameters listed in Table N.5-87.

[List the supported parameters and their supported Values. For detail on the implementation possibilities see Table 8.3.4-1 in PS3.18. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-87. Query Parameters for Search Transaction - Origin Server

Query Parameter	Supported Values	Comments
match	Attribute Values to address the search (matching key). See the supported DICOM Attributes provided in the response in the Table N.5-89
includefield	Attributes to be included in the response (return key). See the supported DICOM Attributes provided in the response in the Table N.5-89
fuzzymatching	<<true false>>
limit
offset	Number of results the server skips before the first returned result

The Search Transaction origin server supports Header Fields listed in Table N.5-88.

[List the supported Header Fields and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-88. Header Fields for Search Transaction - Origin Server

Header Field	Supported Values	Comments
Accept	Received in the user agent request: multipart/related; type="application/dicom+xml" application/dicom+json
Content-Type	Application/dicom+json (Default) Multipart/related; type="application/dicom+xml"
Content-Length		[If Content-Encoding is not present.]
Content-Encoding		[If Content-Length is not present.]

[Indicate which DICOM query Attributes are supported / returned in the response and if they are supported as Matching and/or Return (include) key. If the tables are the same as used in DIMSE Services, you can enter a reference to Table N.5-18 and remove the text and table below. Otherwise provide the following text and Table N.5-89, and add or remove Attributes according to your implementation. In the table below, Attributes / matching /return keys in regular font style are mandatory to be supported.]

Table N.5-89 lists the DICOM query / returned Attributes supported by the Search Transaction origin server.

Table N.5-89. Query / Return Key Search Transaction - Origin Server

Attribute Name	Tag	Comments on the Response
Study Level (May be used for All studies, All series, All instance resource query)
StudyDate	(0008,0020)
StudyTime	(0008,0030)
AccessionNumber	(0008,0050)
ModalitiesInStudy	(0008,0061)
ReferringPhysicianName	(0008,0090)
TimezoneOffsetFromUTC	(0008,0201)	Will be returned if known
Retrieve URL	(0008,1190)	Will be present if the Instance is retrievable by the Retrieve Transaction
PatientName	(0010,0010)
PatientID	(0010,0020)
PatientBirthDate	(0010,0030)
PatientSex	(0010,0040)
StudyInstanceUID	(0020,000D)
StudyID	(0020,0010)
NumberOfStudyRelatedSeries	(0020,1206)
NumberOfStudyRelatedInstances	(0020,1208)
…
Series Level (May be used for All Series, Study's Series, Study's Instances, All Instances resource query)
Modality	(0008,0060)
TimezoneOffsetFromUTC	(0008,0201)	Will be present if known
SeriesDescription	(0008,103E)	Will be present if known
Retrieve URL	(0008,1190)	Will be present if the Instance is retrievable by the Retrieve Transaction
SeriesInstanceUID	(0020,000E)
SeriesNumber	(0020,0011)
NumberOfSeriesRelatedInstances	(0020,1209)
PerformedProcedureStepStartDate	(0040,0244)	Will be present if known
PerformedProcedureStepStartTime	(0040,0245)	Will be present if known
RequestAttributeSequence	(0040,0275)	Will be present if known
> RequestedProcedureID	(0040,1001)
> ScheduledProcedureStepID	(0040,0009)
…
Instance Level (May be used for All instances, Study's instance, Study Series's instance resource query)
SOPClassUID	(0008,0016)
SOPInstanceUID	(0008,0018)
InstanceAvailability	(0008,0056)	Will be present if known
TimezoneOffsetFromUTC	(0008,0201)	Will be present if known
RetrieveURL	(0008,1190)	Will be present if the Instance is retrievable by the Retrieve Transaction
InstanceNumber	(0020,0013)
Rows	(0028,0010)	Will be present if known
Columns	(0028,0011)	Will be present if known
BitsAllocated	(0028,0100)	Will be present if known
NumberOfFrames	(0028,0008)	Will be present if known
…

N.5.3.3 Worklist Web Service

This section provides details regarding the Worklist Web Service. For an overview of supported transactions and resources see Table N.1-10 Worklist Service.

N.5.3.3.1 Create Transaction Worklist Web Service

N.5.3.3.1.1 User Agent

The Worklist Web Service user agent can request resources listed in Table N.5-90 for the Create Workitem Transaction.

[Indicate the supported resources. Remove the non-supported resources rows.Fill in information on your implementation in the Comments column when necessary.]

Table N.5-90. Resources for the Worklist Web Service Create Transaction - User Agent

Resource	Comments
	See resource path in Section 11.4.1.1 in PS3.18
Worklist
Workitems

Table N.5-91 lists the Query parameters supported by Worklist Web Service user agent for the Create Transaction.

[List the supported parameters and their supported Values. See possible parameters / Values in Table 11.1.2-1 in PS3.18. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-91. Query Parameters for Worklist Web Service Create Workitem- User Agent

Query Parameter	Supported Values	Comments

Table N.5-92 lists the Header fields supported by the Worklist Web Service user agent for the Create Transaction.

[List the supported Header fields and their supported Values. See possible Header fields / Values in Table 11.4.1-3 in PS3.18. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-92. Header Fields for Worklist Web Service Create Workitem Worklist Web Service - User Agent

Header Field	Supported Values	Comments

N.5.3.3.1.2 Origin Server

The Worklist Web Service origin server supports resources listed in Table N.5-93 for the Create Transaction:

[Fill in specific details of your implementation if available in the "Comments" column.]

Table N.5-93. Resources for the Worklist Web ServiceCreate Transaction - Origin Server

Resource	Comments
	See resource path in Section 11.4.1.1 in PS3.18
Worklist
Workitems

Table N.5-94 lists the Query parameters supported by Worklist Web Service origin server for the Create Transaction.

[Indicate the supported parameters and their supported Values. See possible parameters / Values in Table 11.4.1-3 in PS3.18. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-94. Query Parameters for Worklist Web Service Create Transaction - Origin Server

Query Parameter	Supported Values	Comments

Table N.5-95 lists the Header fields supported by the Worklist Web Service origin server for the Create Transaction.

Table N.5-95. Header Fields for Worklist Web Service Create Transaction - Origin Server

Header Field	Supported Values	Comments

N.5.3.3.2 Retrieve Transaction Worklist Web Service

N.5.3.3.2.1 User Agent

The Retrieve Workitem Transaction user agent can request resources listed in Table N.5-96.

[Fill in information on your implementation in the Comments column when necessary.]

Table N.5-96. Resources for Worklist Web Service Retrieve Transaction - User Agent

Resource	Comments
	See resource path in Section 11.5.1 in PS3.18
Workitem	/workitems/{workitem}

Table N.5-97 lists the Query parameters supported by Worklist Web Service user agent for the Retrieve Transaction.

[List the supported parameters and their supported Values. See possible parameters / Values in the Table 11.1.2-1 in PS3.18. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-97. Query Parameters for Worklist Web Service Retrieve Workitem Transaction - User Agent

Query Parameter	Supported Values	Comments

Table N.5-98 lists the Header fields supported by the Worklist Web Service user agent for the Retrieve Transaction.

[List the supported Header fields and their supported Values. See possible Header fields / Values in Table 11.5.1-1 in PS3.18. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-98. Header Fields for Worklist Web Service Retrieve Workitem- User Agent

Header Field	Supported Values

N.5.3.3.2.2 Origin Server

The Retrieve Workitem Transaction origin server can request Resources listed in Table N.5-99.

[Fill in specific details of your implementation if available in the "Comments" column.]

Table N.5-99. Resources for Worklist Web Service Retrieve Transaction- Origin Server

Resource	Comments
	See resource path in Section 11.5.1 in PS3.18
Workitem

Table N.5-100 lists the Query parameters supported by Worklist Web Service origin server for the Retrieve Transaction.

[Indicate the supported parameters and their supported Values. See possible parameters / Values in PS 3.18 Table 11.1.2-1. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-100. Query Parameters for Worklist Web Service Retrieve Workitem - Origin Server

Query Parameter	Supported Values	Comments

Table N.5-101 lists the Header fields supported by the Worklist Web Service origin server for the Retrieve Transaction.

Table N.5-101. Header Fields for Worklist Web Service Retrieve Workitem - Origin Server

Header Field	Supported Values	Comments

N.5.3.3.3 Update Transaction Worklist Web Service

N.5.3.3.3.1 User Agent

The Update Workitem Transaction user agent can request resources listed in Table N.5-102.

[Fill in specific details of your implementation if available in the "Comments" column.]

Table N.5-102. Resources for Worklist Web Service Update Transaction - User Agent

Resource	Comments
	See resource path in Section 11.6.1 in PS3.18.
Workitem

Table N.5-103 lists the Query parameters supported by Worklist Web Service user agent for the Update Transaction.

[List the supported parameters and their supported Values. See possible parameters / Values in Section 11.6.1.2 in PS3.18. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-103. Query Parameters for Worklist Web Service Update Transaction - User Agent

Query Parameter	Supported Values	Comments

Table N.5-104 lists the Header fields supported by the Worklist Web Service user agent for the Update Transaction.

[List the supported Header fields and their supported Values. See possible Header fields / Values in Section 11.6.1.3 in PS3.18. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-104. Header Fields for Worklist Web Service Update Transaction - User Agent

Header Field	Supported Values	Comments

N.5.3.3.3.2 Origin Server

The Update Workitem Transaction origin server can request resources listed in Table N.5-105.

[Fill in specific details of your implementation if available in the "Comments" column.]

Table N.5-105. Resources for t Worklist Web Service Update Transaction - Origin Server

Resource	Comments
	See resource path in Section 11.6.1 in PS3.18
Workitem

Table N.5-106 lists the Query parameters supported by Worklist Web Service origin server for the Update Transaction.

Table N.5-106. Query Parameters for Worklist Web Service Update Transaction - Origin Server

Query Parameter	Supported Values	Comments

Table N.5-107 lists the Header fields supported by the Worklist Web Service user agent for the Update Transaction.

Table N.5-107. Header Fields for Worklist Web Service Update Transaction - Origin Server

Header Field	Supported Values	Comments

N.5.3.3.4 Change State Transaction Worklist Web Service

N.5.3.3.4.1 User Agent

The Change State Transaction user agent can request resources listed in Table N.5-108.

Table N.5-108. Resources for Worklist Web Service Change State - User Agent

Resource	Comments
	See resource path in Table 11.1.1-1 in PS3.18.
Workitem State	/workitems/{workitem}/state

Table N.5-109 lists the Query parameters supported by Worklist Web Service user agent for the Change State Transaction.

Table N.5-109. Query Parameters for Worklist Web Service Change State- User Agent

Query Parameter	Supported Values	Comments

Table N.5-110 lists the Header fields supported by the Worklist Web Service user agent for the Change State Transaction.

[List the supported Header fields and their supported Values. See possible Header fields / Values in Table 11.7.1-1 in PS3.18. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-110. Header Fields for Worklist Web Service Change State - User Agent

Header Field	Supported Values	Comments

N.5.3.3.4.2 Origin Server

The Worklist Web Service origin server supports resources listed in Table N.5-111 for the Change State Transaction

Table N.5-111. Resources for Worklist Web Service Change State - Origin Server

Resource	Comments
	See resource path in Table 11.1.1-1 in PS3.18.
Workitem State	/workitems/{workitem}/state

Table N.5-112 lists the Query parameters supported by Worklist Web Service origin server for the Change State Transaction.

Table N.5-112. Query Parameters for Worklist Web Service Change State Transaction - Origin Server

Query Parameter	Supported Values	Comments

Table N.5-113 lists the Header fields supported by the Worklist Web Service origin server for the Change State Transaction.

Table N.5-113. Header Fields for Worklist Web Service Change State Transaction - Origin Server

Header Field	Supported Values	Comments

N.5.3.3.5 Request Cancellation Transaction Worklist Web Service

N.5.3.3.5.1 User Agent

[If your system does not support the Worklist Web Service Request Cancellation Transaction as user agent, you can indicate that this section is not applicable and remove the Table and subsections below.]

The Request Cancellation Transaction user agent can request resources listed in Table N.5-114.

Table N.5-114. Resources for the Worklist Web Service Request Cancellation Transaction - User Agent

Resource	Comments
	See resource path in Section 11.8.1 in PS3.18.
Workitem Request Cancellation	/workitems/{workitem}/cancelrequest

Table N.5-115 lists the Query parameters supported by Worklist Web Service user agent for the Request Cancellation Transaction.

Table N.5-115. Query Parameters for Worklist Web Service Request Cancellation - User Agent

Query Parameter	Supported Values	Comments

Table N.5-116 lists the Header fields supported by the Worklist Web Service user agent for the Request Cancellation Transaction.

[List the supported Header fields and their supported Values. See possible Header fields / Values in Table 11.8.1-1 in PS3.18. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-116. Header Fields for Worklist Web Service Request Cancellation - User Agent

Header Field	Supported Values	Comments

N.5.3.3.5.2 Origin Server

The Worklist Web Service origin server supports resources listed in Table N.5-117 for the Request Cancellation Transaction.

Table N.5-117. Resources for the Worklist Web Service Request Cancellation - Origin Server

Resource	Comments
	See resource path in Section 11.8.1 in PS3.18.
Workitem Request Cancellation	/workitems/{workitem}/cancelrequest

Table N.5-118 lists the Query parameters supported by Worklist Web Service origin server for the Request Cancellation Transaction.

Table N.5-118. Query Parameters for Worklist Web Service Request Cancellation Transaction - Origin Server

Query Parameter	Supported Values	Comments

Table N.5-119 lists the Header fields supported by the Worklist Web Service origin server for the Request Cancellation Transaction.

Table N.5-119. Header Fields for Worklist Web Service Request Cancellation Transaction - Origin Server

Header Field	Supported Values	Comments

N.5.3.3.6 Search Transaction Worklist Web Service

N.5.3.3.6.1 User Agent

The Search Transaction user agent can request resources listed in Table N.5-120.

Table N.5-120. Resources for Worklist Web Service Search Transaction - User Agent

Resource	Comments
	See resource path in Section 11.9.1 in PS3.18.
Workitem	/workitems

Table N.5-121 lists the Query parameters supported by Worklist Web Service user agent for the Search Transaction.

[List the supported parameters and their supported Values. See possible parameters / Values in Table 8.3.4-1 in PS3.18. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-121. Query Parameters for Worklist Web Service Search Transaction - User Agent

Query Parameter	Supported Values	Comments

Table N.5-122 lists the Header fields supported by the Worklist Web Service user agent for the Search Transaction.

[List the supported Header fields and their supported Values. See possible Header fields / Values in Table 11.9.1-1 in PS3.18. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-122. Header Fields for Worklist Web Service Search Transaction - User Agent

Header Field	Supported Values	Comments

N.5.3.3.6.2 Origin Server

The Worklist Web Service origin server supports resources listed in Table N.5-123 for the Search Transaction.

Table N.5-123. Resources for Worklist Web Service Search Transaction - Origin Server

Resource	Comments
	See resource path in Section 11.9.1 in PS3.18.
Workitem	/workitems?{&match*}{&includefield}{&fuzzymatching}{&offset}{&limit}

Table N.5-124 lists the Query parameters supported by Worklist Web Service origin server for the Search Transaction.

Table N.5-124. Query Parameters for Worklist Web Service Search Transaction - Origin Server

Query Parameter	Supported Values	Comments

Table N.5-125 lists the Header fields supported by the Worklist Web Service origin server for the Search Transaction.

Table N.5-125. Header Fields for Worklist Web Service Search Transaction - Origin Server

Header Field	Supported Values	Comments

N.5.3.3.7 Subscribe Transaction Worklist Web Service

[If your system does not support the Worklist Web Service Subscribe Transaction, you can indicate that this section is not applicable and remove the subsections below.]

N.5.3.3.7.1 User Agent

The Subscribe Transaction user agent can request resources listed in Table N.5-126.

[List the supported resources. Remove the non-supported resources rows. Fill in specific details of your implementation if available in the "Comments" column.]

Table N.5-126. Resources for Worklist Web Service Subscribe Transaction - User Agent

Resource	Comments
	See resource path in Table 11.10.1-1 in PS3.18.
Worklist	/workitems/1.2.840.10008.5.1.4.34.5/subscribers/{aetitle}
Filtered Worklist	/workitems/1.2.840.10008.5.1.4.34.5.1/subscribers/{aetitle}
Workitem	/workitems/{workitem}/subscribers/{aetitle}

Table N.5-127 lists the Query parameters supported by Worklist Web Service user agent for the Subscribe Transaction.

[List the supported parameters and their supported Values. See possible parameters / Values in Table 11.10.1-2 in PS3.18. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-127. Query Parameters for Worklist Web Service Subscribe Transaction - User Agent

Query Parameter	Supported Values	Comments

Table N.5-128 lists the Header fields supported by the Worklist Web Service user agent for the Subscribe Transaction:

[List the supported Header fields and their supported Values. See possible Header fields / Values in Table 8.4.1-1 in PS3.18. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-128. Header Fields for Worklist Web Service Subscribe Transaction - User Agent

Header Field	Supported Values	Comments

N.5.3.3.7.2 Origin Server

The Worklist Web Service origin server supports resources listed in Table N.5-129 for the Subscribe Transaction.

[List the supported resources. Remove the non-supported resources rows. Fill in specific details of your implementation if available in the "Comments" column.]

Table N.5-129. Resources for Worklist Web Service Subscribe Transaction - Origin Server

Resource	Comments
	See resource path in Table 11.10.1-1 in PS3.18.
Worklist	/workitems/1.2.840.10008.5.1.4.34.5/subscribers/{aetitle}
Filtered Worklist	/workitems/1.2.840.10008.5.1.4.34.5.1/subscribers/{aetitle}
Workitem	/workitems/{workitem}/subscribers/{aetitle}

Table N.5-130 lists the Query parameters supported by Worklist Web Service origin server for the Subscribe Transaction.

Table N.5-130. Query Parameters for Worklist Web Service Subscribe Transaction - Origin Server

Query Parameter	Supported Values	Comments

Table N.5-131 lists the Header fields supported by the Worklist Web Service origin server for the Subscribe Transaction.

[List the supported Header fields and their supported Values. See possible Header fields / Values in the DICOM Table 8.4.1-1 in PS3.18. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-131. Header Fields for Worklist Web Service Subscribe Transaction - Origin Server

Header Field	Supported Values	Comments

N.5.3.3.8 Unsubscribe Transaction Worklist Web Service

N.5.3.3.8.1 User Agent

The Unsubscribe Transaction user agent can request resources listed in Table N.5-132.

[List the supported resources. Remove the non-supported resources rows. Fill in specific details of your implementation if available in the "Comments" column.]

Table N.5-132. Resources for Worklist Web Service Unsubscribe Transaction - User Agent

Resource	Comments
	See resource path in Table 11.11.1-1 in PS3.18.
Workitem	workitems/{workitem}/subscribers/{aetitle}
Worklist	/workitems/1.2.840.10008.5.1.4.34.5/subscribers/{aetitle}
Filtered Worklist	/workitems/1.2.840.10008.5.1.4.34.5.1/subscribers/{aetitle}

Table N.5-133 lists the Header fields supported by the Worklist Web Service user agent for the Unsubscribe Transaction.

Table N.5-133. Header Fields for Worklist Web Service Unsubscribe Transaction- User Agent

Header Field	Supported Values	Comments

N.5.3.3.8.2 Origin Server

The Worklist Web Service origin server supports resources listed in Table N.5-134 for the Unsubscribe Transaction.

Table N.5-134. Resources for Worklist Web Service Unsubscribe Transaction - Origin Server

Resource	Comments
	See resource path in Table 11.11.1-1 in PS3.18.
Workitem	workitems/{workitem}/subscribers/{aetitle}
Worklist	/workitems/1.2.840.10008.5.1.4.34.5/subscribers/{aetitle}{/suspend}
Filtered Worklist	/workitems/1.2.840.10008.5.1.4.34.5.1/subscribers/{aetitle}{/suspend}

Table N.5-135 lists the Header fields supported by the Worklist Web Service origin server for the Unsubscribe Transaction.

Table N.5-135. Header Fields for Worklist Web Service Unsubscribe Transaction - Origin Server

Header Field	Supported Values	Comments

N.5.3.3.9 Suspend Global Subscription Transaction Worklist Web Service

N.5.3.3.9.1 User Agent

The Suspend Global Subscription Transaction user agent can request resources listed in Table N.5-136.

[List the supported resources. Remove the non-supported resources rows. Fill in specific details of your implementation if available in the "Comments" column.]

Table N.5-136. Resources for Worklist Web Service Suspend Global Subscription Transaction - User Agent

Resource	Comments
	See resource path in Table 11.12.1-1 in PS3.18
Worklist	/workitems/1.2.840.10008.5.1.4.34.5/subscribers/{aetitle}{/suspend}
Filtered Worklist	/workitems/1.2.840.10008.5.1.4.34.5.1/subscribers/{aetitle}{/suspend}

Table N.5-137 lists the Header fields supported by the Worklist Web Service user agent for the Suspend Global Subscription Transaction.

Table N.5-137. Header Fields for Worklist Web Service Suspend Global Subscription Transaction - User Agent

Header Field	Supported Values	Comments

N.5.3.3.9.2 Origin Server

The Worklist Web Service origin server supports resources listed in Table N.5-138 for the Suspend Global Subscription Transaction.

Table N.5-138. Resources for Worklist Web Service Suspend Global Subscription Transaction - Origin Server

Resource	Comments
	See resource path in Table 11.12.1-1 in PS3.18
Worklist	/workitems/1.2.840.10008.5.1.4.34.5/subscribers/{aetitle}{/suspend}
Filtered Worklist	/workitems/1.2.840.10008.5.1.4.34.5.1/subscribers/{aetitle}{/suspend}

Table N.5-139 lists the Header fields supported by the Worklist Web Service origin server for the Suspend Global Subscription Transaction.

Table N.5-139. Header Fields for Worklist Web Service Suspend Global Subscription Transaction - Origin Server

Header Field	Supported Values	Comments

N.5.3.4 Non-Patient Instance Web Service

This section provides details regarding the Non-Patient Instance Web Service. For an overview of supported Transactions and resources see Table N.1-11 Non-Patient Instance Service.

N.5.3.4.1 Supported Web Media Types

The supported Non-Patient Instance Storage SOP Classes are listed in the Table N.5-140 below. The supported Transfer Syntaxes are listed in Section N.1.1 of this document.

[Indicate which SOP Classes are supported by your system. Remove the unsupported ones. See possible NPI SOP Classes in PS 3.4 Table GG.3-1

In the URI user agent / origin server columns use Y or N to indicate Support for the listed SOP Class.If SOP Class is neither supported as user agent nor origin server, remove row.]

Table N.5-140. Non-Patient Instance Web Service Storage SOP Classes

SOP Classname	SOP Class UID	User Agent	Origin Server	Comments
Hanging Protocol Storage	1.2.840.10008.5.1.4.38.1
Color Palette Storage	1.2.840.10008.5.1.4.39.1
Generic Implant Template Storage	1.2.840.10008.5.1.4.43.1
Implant Assembly Template Storage	1.2.840.10008.5.1.4.44.1
Implant Template Group Storage	1.2.840.10008.5.1.4.45.1
CT Defined Procedure Protocol Storage	1.2.840.10008.5.1.4.1.1.200.1
Protocol Approval Storage	1.2.840.10008.5.1.4.1.1.200.3

N.5.3.4.2 Retrieve Transaction

N.5.3.4.2.1 User Agent

The Non-Patient Instance (NPI) Retrieve transaction as user agent can request resources listed in Table N.5-141

[Provide implementation specific details in the "Comments" column and indicate the supported {npi-name}. They can be:

color-palettes
defined-procedure-protocols
hanging-protocols
implant-templates]

Table N.5-141. Resources for NPI Web Services Retrieve Transaction - User Agent

Resource	Comments
	See resource path in Table 12.4.1-1 in PS3.18
Instance	/{npi-name}/{uid}

Table N.5-142 lists the Query parameters supported by the NPI Web Service user agent for the Retrieve Transaction.

[List the supported parameters and their supported Values. See possible parameters / Values in Table 12.1.2-1 in PS3.18. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-142. Query Parameters for NPI Web Services Retrieve Transaction - User Agent

Query Parameter	Supported Values	Comments

Table N.5-143 lists the Header Fields supported by the NPI Web Service user agent for the Retrieve Transaction.

[List the supported Header fields and their supported Values. See possible Header fields / Values Section 12.4.1.3 in PS3.18. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-143. Header Fields for NPI Web Services Retrieve Transaction - User Agent

Header Field	Supported Values	Comments

N.5.3.4.2.2 Origin Server

The NPI Web Service origin server supports resources listed in Table N.5-144 for the Retrieve Transaction:

[Provide implementation specific details in the "Comments" column and indicate the supported {npi-name}. They can be:

color-palettes
defined-procedure-protocols
hanging-protocols
implant-templates]

Table N.5-144. Resources for NPI Web Services Retrieve Transaction - Origin Server

Resource	Comments
	See resource path in Table 12.4.1-1 in PS3.18
Instance	/{npi-name}/{uid}

Table N.5-145 lists the Query parameters supported by the NPI Web Service origin server for the Retrieve Transaction.

Table N.5-145. Query Parameters for NPI Web Services Retrieve Transaction - Origin Server

Query Parameter	Supported Values	Comments

Table N.5-146 lists the Header Fields supported by the NPI Web Service origin server for the Retrieve Transaction.

[List the supported Header fields and their supported Values. See possible Header fields / Values in Section 12.4.1.3 in PS3.18 and Section 12.4.3.2 in PS3.18. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-146. Header Fields for NPI Web Services Retrieve Transaction - Origin Server

Header Field	Supported Values	Comments

N.5.3.4.3 Store Transaction

N.5.3.4.3.1 User Agent

For details regarding the IODs created by the system, see Section N.9.

The NPI Store Transaction user agent can request resources listed in Table N.5-147.

[List the supported resources. Remove the non-supported resources rows.

Provide implementation specific details in the "Comments" column and indicate what the supported {npi-name} are. They can be:

color-palettes
defined-procedure-protocols
hanging-protocols
implant-templates]

Table N.5-147. Resources for NPI Web Services Store Transaction - User Agent

Resource	Comments
	See resource path in Table 12.5.1-1 in PS3.18.
All Instances	/{npi-name}
Instance	/{npi-name} {/uid}

Table N.5-148 lists the Query parameters supported by the NPI Web Service user agent for the Store Transaction.

Table N.5-148. Query Parameters for NPI Web Services Store Transaction - User Agent

Query Parameter	Supported Values	Comments

Table N.5-149 lists the Header fields supported by the NPI Web Service user agent for the Store Transaction.

[List the supported Header fields and their supported Values. See possible Header fields / Values in Section 12.5.1.3 in PS3.18. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-149. Header Fields for NPI Web Services Store Transaction - User Agent

Header Field	Supported Values	Comments

N.5.3.4.3.2 Origin Server

The NPI Store Transaction origin server receives POST requests to store or append to an existing resource on the server.

The user agent specifies the Target Resource as part of the URI and encapsulates the data in a multipart request body with a proper Content-Type (i.e., BINARY, XML or JSON).

The URI is composed by a Base URI: see Base URI for the origin server in Section N.6.3.4.

The NPI Store Transaction origin server supports resources listed in Table N.5-150.

[List the supported resources. Remove the non-supported resources rows.

Provide implementation specific details in the "Comments" column and indicate what are the supported {npi-name}. They can be:

color-palettes
defined-procedure-protocols
hanging-protocols
implant-templates]

Table N.5-150. Resources for NPI Web Services Store Transaction - Origin Server

Transaction

Resource

Comments

See resource path in Table 12.5.1-1 in PS3.18.

Store

(a set of instances)

All Instances

Store

(a single instance)

Instance

Table N.5-151 lists the Query parameters supported by the NPI Web Service origin server for the Store Transaction.

Table N.5-151. Query Parameters for NPI Web Services Store Transaction - Origin Server

Query Parameter	Supported Values	Comments

Table N.5-152 lists the Header fields supported by the NPI Web Service origin server for the Store Transaction.

[List the supported Header fields and their supported Values. See possible Header fields / Values in Section 12.5.1.3 in PS3.18 Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-152. Header Fields for NPI Web Services Store Transaction - Origin Server

Header Field	Supported Values	Comments

N.5.3.4.4 Search Transaction

N.5.3.4.4.1 User Agent

The NPI Search Transaction user agent can request resources listed in Table N.5-153.

[Provide implementation specific details in the "Comments" column and indicate what are the supported {npi-name}. They can be:

color-palettes
defined-procedure-protocols
hanging-protocols
implant-templates]

Table N.5-153. Resources for NPI Web Services Search Transaction - User Agent

Resource	Comments
	See resource path in Table 12.6.1-1 in PS3.18.
All Instances	/{npi-name}

Table N.5-154 lists the Query parameters supported by the NPI Web Service user agent for the Search Transaction.

[List the supported parameters and their supported Values. See possible parameters / Values in Section 12.1.2 in PS3.18 and Table 8.3.4-1 in PS3.18. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-154. Query Parameters for NPI Web Services Search Transaction - User Agent

Query Parameter	Supported Values	Comments

Table N.5-155 lists the DICOM query Attributes supported by the NPI Web Service user agent for the Search Transaction.

[Indicate which DICOM query Attributes are supported and if they are supported as Matching and/or Return (include) key. See PS 3.18 Table 12.6.1-2]

Table N.5-155. Supported Query Attributes for NPI Web Services Search Transaction - User Agent

Attribute Name	Tag	Matching Key	Return Key	Comments

Table N.5-156 lists the Header fields supported by the NPI Web Service user agent for the Search Transaction.

[List the supported Header fields and their supported Values. See possible Header fields / Values in Section 12.6.1.3 in PS3.18 Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-156. Header Fields for NPI Web Services Search Transaction - User Agent

Header Field	Supported Values	Comments

N.5.3.4.4.2 Origin Server

The NPI Search Transaction origin server receives GET requests to search for studies, series or instances.

[Specify here if this is a native or a DIMSE proxy implementation.]

The user agent specifies the Target Resource as part of the URI and the acceptable response Content-Type in the HTTP Header (i.e., dicom+xml or dicom+json).

The URI is composed by a Base URI: see Base URI for the origin server in Section N.6.3.4.

The Search Transaction origin server supports resources listed in Table N.5-157.

[Provide implementation specific details in the "Comments" column and indicate the supported {npi-name}. They can be:

color-palettes
defined-procedure-protocols
hanging-protocols
implant-templates]

Table N.5-157. Resources for NPI Web Services Search Transaction - Origin Server

Resource	Comments
	See resource path in Table 12.6.1-1 in PS3.18.
All Instances	/{npi-name}

Table N.5-158 lists the Query parameters supported by the NPI Web Service origin server for the Search Transaction.

Table N.5-158. Query Parameters for NPI Web Services Search Transaction - Origin Server

Query Parameter	Supported Values	Comments

[List the supported Header fields and their supported Values. See possible Header fields / Values in Section 12.6.1.3 in PS3.18 and Section 12.6.3.2 in PS3.18 Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-159. Header Fields for NPI Web Services Search Transaction - Origin Server

Header Field	Supported Values	Comments

Table N.5-160 lists the DICOM query / returned Attributes supported by the NPI Web Service origin server for the Search Transaction.

[Indicate which DICOM query Attributes are supported / returned in the response and if they are supported as Matching and/or Return (include) key. See Table 12.6.1-2 in PS3.18]

Table N.5-160. Query / Return Key for NPI Web Services Search Transaction - Origin Server

Attribute Name	Tag	Matching Key	Return Key	Comments on the response

N.5.3.5 Notification Web Service

[If your Web Service supports notification, describe how WebSocket connections are opened. See details in Section 8.10 in PS3.18]

N.5.3.6 Storage Commitment Web Service

This section provides details regarding the Storage Commitment Web Service. For an overview of suppported Transactions and resources see Table N.1.3.5-1 Storage Commitment Service

N.5.3.6.1 Request Transaction - Storage Commitment Service

N.5.3.6.1.1 User Agent

The Request Transaction user agent can request resources listed in Table N.5.3.6.1.1-1.

[List the supported resources for your Storage Commitment Request Transaction user agent. Remove the non-supported resources rows. Fill in information on your implementation in the Comments column when necessary.]

Table N.5.3.6.1.1-1. Resources for Request Transaction - User Agent

Resource	Comments
	See Resources path in Table 13.1.1-1 in PS3.18
Commitment-requests

The Request Transaction user agent supports Header Fields listed in Table N.5.3.6.1.1-2.

[List the supported Header Fields and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5.3.6.1.1-2. Header Fields for Request Transaction - User Agent

Header Field	Supported Values	Comments
Content-Type	application /dicom+json application /dicom+xml multipart/related; type="application/dicom+json" multipart/related; type="application/dicom+xml"
Content-Length		[If Content-Encoding is not present]
Content-Encoding		[If Content-Length is not present]

N.5.3.6.1.2 Origin Server

The Request Transaction origin server receives POST requests for storage commitment of the referenced SOP Instances.

The user agent specifies the Target Resource as part of the URI and specifies the UIDs of the SOP Instances as part of the data in the request body with an appropriate Content-Type (i.e., XML or JSON).

The URI is composed by a Base URI: see Base URI for the origin server in Section N.6.3.5.

The Request Transaction origin server supports resources listed in Table N.5.3.6.1.2-1.

[Fill in information on your implementation in the Comments column when necessary.]

Table N.5.3.6.1.2-1. Resources for Request Transaction - Origin Server

Resource	Comments
	See Resources path in Table 13.1.1-1 in PS3.18
commitment-requests

The Request Transaction origin server supports Header Fields listed in Table N.5.3.6.1.2-2.

[List the supported Header Fields and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5.3.6.1.2-2. Header Fields for Request Transaction - Origin Server

Header Field	Supported Values	Comments
Content-Type	application /dicom+json application /dicom+xml multipart/related; type="application/dicom+json" multipart/related; type="application/dicom+xml"
Content-Length		[If Content-Encoding is not present]
Content-Encoding		[If Content-Length is not present]

N.5.3.6.2 Result Check Transaction - Storage Commitment Service

N.5.3.6.2.1 User Agent

The resources and header fields supported by the user agent for the Result Check Transaction are the same as for the Request Transaction; see Section N.5.3.6.1.1.

N.5.3.6.2.2 Origin Server

The Result Check Transaction origin server receives GET requests to check whether there is a result for a storage commitment request.

The Base URI, resources, and header fields supported by the origin server for the Result Check Transaction are the same as for the Request Transaction; see Section N.5.3.6.1.2.

N.5.4 Media Services

N.5.4.1 File Set Creator (FSC)

<Product> supports creating the Basic Directory IOD as a File Set Creator as defined in Section N.9.5.

For a list of supported Media Application Profiles, see Section N.1.4 in the Overview.

For a list of supported SOP Classes, see Section N.1.1 in the Overview.

[Describe, how the File Set Creator is selecting the Media Application Profiles used for creating the Media.]

N.5.4.2 File Set Reader (FSR)

<Product> supports the Media Application Profiles listed in Section N.1.4 in the Overview.

For a list of supported SOP Classes, see Section N.1.1 in the Overview.

[Provide requirements for display and processing of instances contained on the medium. This could either be done by referencing Section N.5.2.5.2 (as indicated below), if the same requirements apply, or by copying the tables from Section N.5.2.5.2 and filling them appropriately, if requirements for external media differ.]

To display or process DICOM Instances contained on the Media, see Section N.5.2.5.2.

N.5.4.3 File Set Updater (FSU)

<Product> supports creating the Basic Directory IOD as defined in Section N.9.5.

For a list of supported Media Application Profiles, see Section N.1.4 in the Overview.

For a list of supported SOP Classes, see Section N.1.1 in the Overview.

N.5.5 Real-Time Video Services

N.5.5.1 Service Consumer

For a list of supported SOP Classes, see Section N.1.5 in the Overview.

Table N.5-161 lists restrictions that apply to the RTV instances supported by the Service Consumer.

[List the restrictions for the RTV Service Consumer in Table N.5-161 below.]

Table N.5-161. DICOM-RTV Instances Specification Service Consumer

Category	Restrictions
Photometric Interpretation	RGB
Bit depth (video)	10
Number of Waveform Channels	2
Bit depth (audio)	16 (signed 16-bits linear)
Sampling Frequency	48 kHz

Table N.5-162 lists the screen resolutions that are supported by the Service Consumer.

[List all supported screen resolutions in Table N.5-162 below.]

Table N.5-162. DICOM-RTV Screen Resolutions Service Consumer

Rows	Columns	Frame rate	Video Type	Progressive or Interlaced
1080	1920	25	25 Hz HD	P
1080	1920	29.97, 30	30 Hz HD	P
1080	1920	25	25 Hz HD	I
1080	1920	29.97, 30	30 Hz HD	I
720	1280	25	25 Hz HD	P
720	1280	29.97, 30	30 Hz HD	P
720	1280	50	50 Hz HD	P
720	1280	59.94, 60	60 Hz HD	P

[Provide the connection policies including access to the URL to retrieve the SDP object and the number of simultaneous connections.]

N.5.5.2 Service Provider

For a list of supported SOP Classes, see Section N.1.5 in the Overview.

Table N.5-163 list restrictions that apply to the RTV instances supported by the Service Provider.

[List the restrictions for the RTV Service Consumer in Table N.5-163 below.]

Table N.5-163. DICOM-RTV Instances Specification Service Provider

Category	Restrictions
Photometric interpretation	RGB
Bit depth (video)	10
Number of Waveform Channels	2
Bit depth (audio)	16 (signed 16-bits linear)
Sampling Frequency	48 kHz

Table N.5-164 list the screen resolutions that are supported by the Service Provider.

[List all supported screen resolutions in Table N.5-164 below.]

Table N.5-164. DICOM RTV Screen Resolutions Service Provider

Rows	Columns	Frame rate	Video Type	Progressive or Interlaced
1080	1920	25	25 Hz HD	P
1080	1920	29.97, 30	30 Hz HD	P
1080	1920	25	25 Hz HD	I
1080	1920	29.97, 30	30 Hz HD	I
720	1280	25	25 Hz HD	P
720	1280	29.97, 30	30 Hz HD	P
720	1280	50	50 Hz HD	P
720	1280	59.94, 60	60 Hz HD	P

[Provide the connection policies including the URL where the Service Consumer can retrieve the SDP object and the number of simultaneous connections.]

N.5.6 Cross Service Considerations

This section describes interaction between the implementation of different DICOM Services in this product. Details internal to an individual service are addressed in previous Service Sections.

Note

Note: The DICOM Standard typically does not define cross-service requirements. Therefore, this section provides an implementation description and is not strictly required DICOM Conformance.

[Describe any cross-service interactions, e.g., the MPPS COMPLETED message is sent when the archiving of related Instances in the Study is finished. If there are no Cross Service Considerations remove the text above and mark the section as N/A.]

N.5.7 Specific Character Sets

See Section N.1.7 for supported Values for Specific Character Set (0008,0005).

Generic configuration for Specific Character Sets is covered in . Service specific configuration for Specific Character Sets is addressed in respective subsections of Section N.6.2 or Section N.6.3.

Describe behaviors such as the whether your product sends value 1, e.g.,

This product omits Value 1 of Specific Character Set (0008,0005) when multiple values are present. Per PS3.5, the empty Value 1 indicates usage of ISO 2022 IR 6.]

[Describe the presentation of the characters to a user, i.e., capabilities, font limitations and/or substitutions of characters.]

[If your product supports display/editing of non-default Character Sets, fill in the following table, otherwise remove the following table and introductory text.]

<Product> supports displaying character sets beyond the default character repertoire (ISO-IR 6) for all displayed attributes.

<Product> supports editing character sets beyond the default character repertoire (ISO-IR 6) for the attributes listed in Table N.5-164a.

Table N.5-164a. Specific Character Set – Supported Attributes

Attribute Name	Tag	VR
Referring Physician's Name	(0008,0090)	PN
Study Description	(0008,1030)	LO
Series Description	(0008,103E)	LO
Operators' Name	(0008,1070)	PN
Patient's Name	(0010,0010)	PN
Other Patient Names	(0010,1001)	PN
Patient's Address	(0010,1040)	LO
Allergies	(0010,2110)	LO
Patient Comments	(0010,4000)	LT
…

[If your product supports mapping/conversion of non-default Character Sets, fill in the table below, otherwise remove the table and the introductory text below.]

<Product> supports mapping/conversion of Character Sets as listed in Table N.5-165.

[Describe how Specific Character Sets that are received by the system are mapped to Specific Character Sets sent out by the system. It does not consider the Character Set used internally within the product. In the "Mapping Situation" column describe the scenario in which this mapping occurs, e.g., when mapping Character Sets from a Modality Worklist entry or a Query Retrieve response to the instances created.]

Table N.5-165. Conversion/Mapping of Non-Default Specific Character Sets

Incoming Specific Character Set			Outgoing Specific Character Set			Mapping Situation
Defined Term	IANA	Description	Defined Term	IANA	Description	Mapping Situation
ISO 2022 IR 87	ISO-2022-JP	Japanese	ISO_IR 192	UTF-8	Unicode in UTF-8	When mapping Attribute Values from MWL to instances created

[Explain your product behavior in case it encounters unsupported character sets.]

N.6 Configuration

[Briefly describe if there is a configuration interface (service tool, administration GUI, web interface, or other) to configure the basic parameters.]

Throughout all subsections the following Values can be used in the "Configurable" column:

USER: The parameter is configurable by the user.
SERVICE: The parameter is configurable by service personnel.
FIXED: The parameter is not configurable (it has a fixed Value). The Value is required for the configuration of the remote system.
N/A: The parameter is not applicable for the local or the remote system.

N.6.1 General Configuration Parameters

Table N.6-1 lists general configuration parameters applicable across all supported DICOM Services.

Table N.6-1. General Configuration Parameters

Parameter	Configurable	Default Value	Comments
[Fill in general parameters related to DICOM connections such as timeouts.]	<<USER SERVICE FIXED N/A>>	[If no default Value, leave it blank.]	[Optionally put a comment that would help the reader to understand the configuration/parameter and list Value ranges if applicable.]
General Parameters
Timeout waiting for acceptance or rejection Response to an Association Open Request. (Application-Level timeout)
Timeout waiting for a response to an Association release request (Application Level Timeout)
General DIMSE level timeout Values
TCP/IP Settings
TCP/IP Send Buffer	SERVICE	65535 Bytes	Min: 16Kb, Max: 128Kb
TCP/IP Receive Buffer	FIXED	65535 Bytes
DICOM Services Parameters
Maximum number of simultaneous Associations accepted
Specific Character Set			[If character set is configurable per service, add the Specific Character Set configuration row in the relevant services.]
Other parameters

N.6.2 Configuration of DIMSE Services

The tables in the following subsections show the configuration parameters required for DIMSE Services.

In order to identify whether <product> is an SCP and/or an SCU, the following applies:

SCP: The (Secured) Local Called AET and Remote Calling AET parameters are present.
SCU: The (Secured) Local Calling AET and Remote Called AET parameters are present.

[Use this table template in each supported DIMSE Service section, similar to the example tables provided and provide information as needed for the product implementation. "Local Configuration Parameters" describes parameters for the product described in this DCS, whereas "Remote Configuration Parameters" describes the information needed for this product to interface with a remote system.

Remove rows for any unsupported parameters. For example, if <product> is an SCU only, remove the rows for Called AE Title and Ports in the Local Configuration Parameters part of the table and the Calling AE Title row in the Remote Configuration Parameters part. If <product> is an SCP only, remove the Calling AE Title row in the Local Configuration Parameters part and remove the rows for the Called AE Title, Ports and Host from the Remote Configuration Parameters part.

If your product implementation supports multiple AE Titles for the same service, list all of them in separate rows and describe their use in the "Comments" column.

Local Configuration Parameters - <service name>
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
Calling AE Title (SCU)
Called AE Title (SCP)
Port
TLS-Secured Port
<Specific service parameter>
Remote Configuration Parameters - <service name>
[Either document the number of supported remote hosts, e.g <Product> supports configuration of up to <X> remote hosts, or state that there is no limitation other than the ones mandated by the operating system.]
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
Calling AE Title (SCU)
Called AE Title (SCP)
Port
TLS-Secured Port
Host
<Specific service parameters>

]

N.6.2.1 Basic Worklist Management Service Configuration

Table N.6-2 lists Worklist Service configuration parameters:

Table N.6-2. Worklist Service Parameters

Parameter	Configurable	Default Value	Comments
Local Configuration Parameters - Worklist Service
[This example shows configuration for an MWL SCU, e.g., a modality.]	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
Calling AE Title (SCU)	SERVICE	WORKLIST_AE
Default Modality type	USER	CR	Used to query the MWL SCP. Possible choices are CR, DX, RF
Default Scheduled Station AE Title	SERVICE		Used to query the remote MWL SCP
Remote Configuration Parameters - Worklist Service
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
Called AE Title (SCP)	SERVICE		Can connect up to 3 RIS
Port	SERVICE	104
TLS-Secured Port	FIXED	2762
Host	SERVICE

N.6.2.2 Modality Performed Procedure Step Service Configuration

Table N.6-3 lists Modality Performed Procedure Step Service configuration parameters:

Table N.6-3. MPPS Service Parameters

Local Configuration Parameters - MPPS Service
Parameter	Configurable	Default Value	Comments
[This example shows configuration for an MPPS SCU and SCP, e.g., a PACS.]	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
Calling AE Title (SCU)	SERVICE	STORE_AE	The system uses the same Calling AE Title as for the Storage SCU service by default
Called AE Title (SCP)	SERVICE	STORE_AE	The system uses the same called AE Title as for the Storage SCP service by default
Port	FIXED	104
TLS-Secured Port	FIXED	2762
Remote Configuration Parameters - MPPS Service
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
Calling AE Title (SCU)	SERVICE
Called AE Title (SCP)	SERVICE
Port	SERVICE	104
TLS-Secured Port	SERVICE	2762
Host	SERVICE
Rely on MPPS complete sent by modality	SERVICE	unchecked	If checked the PPS will be considered as completed when the modality sends the MPPS N-SET COMPLETED

N.6.2.3 Unified Worklist and Procedure Step Service Configuration

Table N.6-4 lists Unified Worklist and Procedure Step Service configuration parameters:

Table N.6-4. Unified Worklist and Procedure Step Service Parameters

Parameter	Configurable	Default Value	Comments
Local Configuration Parameters - Unified Worklist and Procedure Step Service
[This example shows configuration for an UPS SCU, e.g., a Modality acting as a workitem creator]	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
Calling AE Title (SCU)	SERVICE	WORKLIST_AE
Remote Configuration Parameters - Unified Worklist and Procedure Step Service
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
Called AE Title (SCP)	SERVICE
Port	SERVICE	104
TLS-Secured Port	SERVICE	2762
Host	SERVICE

N.6.2.4 Instance Availability Notification Service Configuration

Table N.6-5 lists Instance Availability Notification Service configuration parameters:

Table N.6-5. IAN Service Parameters

Parameter	Configurable	Default Value	Comments
Local Configuration Parameters - Instance Availability Notification Service
[This example shows configuration for an IAN SCU, e.g., a PACS.]	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
Calling AE Title (SCU)	SERVICE	IAN_AE
Remote Configuration Parameters - Instance Availability Notification Service
[Either document the number of supported remote hosts, e.g <Product> supports configuration of up to <X> remote hosts, or state that there is no limitation other than the ones mandated by the operating system.]
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
Called AE Title (SCP)	SERVICE
Port	SERVICE	104
Host	SERVICE

N.6.2.5 Storage Service Configuration

Table N.6-6 lists Storage Service configuration parameters:

Table N.6-6. Storage Service Parameters

Local Configuration Parameters - Storage Service
Parameter	Configurable	Default Value	Comments
[This example shows the configuration for a Storage SCU and SCP, e.g., a PACS.]	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
Calling AE Title (SCU)	SERVICE	STORE_AE
Called AE Title (SCP)	SERVICE	STORE_AE	List of AE Titles can be configured depending on the usage (study to be verified or not; studies not to be archived; study to be displayed only…)
Port	FIXED	104	For studies to be displayed only (not imported in DB/cache, the default port is 110)
TLS-Secured Port	FIXED	2762
Supported Transfer Syntax as SCP	SERVICE	See Table N.1-2	Can force to accept ILE only
Supported Storage SOP Classes as SCP	SERVICE	See Table N.1-1	Can add or remove Storage SOP Classes
Remote Configuration Parameters - Storage Service
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
Calling AE Title (SCU)	SERVICE
Called AE Title (SCP)	SERVICE
Port	SERVICE	104
Host	SERVICE
Inbound PID / issuer to use	SERVICE		In case the remote Storage SCU does not send an issuer of Patient ID, you can define a default inbound Patient ID issuer.
Outbound Issuer of Patient ID default	SERVICE		In case there are several PID/issuers for the study to send, the default PID/issuer can be selected to be sent as the primary Patient ID to the remote storage SCP

N.6.2.6 Storage Commitment Service Configuration

Table N.6-7 lists Storage Commitment Service configuration parameters:

Table N.6-7. Storage Commitment Service Parameters

Local Configuration Parameters - Storage Commitment Service
Parameter	Configurable	Default Value	Comments
[This example shows the for a Storage Commitment SCU and SCP, e.g., a PACS.]	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
Calling AE Title (SCU)	SERVICE	STORE_AE	The system uses the same Calling AE Title as for the Storage SCU service by default
Called AE Title (SCP)	SERVICE	STORE_AE	The system uses the same Called AE Title as for the Storage SCP service by default
Port	SERVICE	104
TLS-Secured Port	FIXED	2762
Delay to send N-ACTION-RQ	SERVICE	300
Delay to send N-EVENT-REPORT-RQ	FIXED	immediately	As soon as the N-ACTION-RQ is received the system will initiate an Association to send the N-EVENT-REPORT
N-EVENT-REPORT on same Association	FIXED	asynchronous	When the system receives a N-ACTION, it will open a new Association to send the N-EVENT-REPORT. When the system sends an N-ACTION, it expects to receive the N-EVENT-REPORT in a separate Association.
Remote Configuration Parameters - Storage Commitment Service
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
Calling AE Title (SCU)	SERVICE
Called AE Title (SCP)	SERVICE
port	SERVICE	104
TLS-Secured Port	SERVICE	2762
Host	SERVICE

N.6.2.7 Query/Retrieve Service Configuration

Table N.6-8 lists Query/Retrieve Service configuration parameters:

Table N.6-8. Query/Retrieve Service Parameters

Local Configuration Parameters - Query/Retrieve Service
Parameter	Configurable	Default Value	Comments
[This example shows the configuration for a Query / Retrieve SCU and SCP, e.g., a PACS.]	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
Calling AE Title (SCU)	SERVICE	QUERY_AE	The same Calling AET is used for Query and Retrieve
Called AE Title (SCP)	SERVICE	QUERY_AE	The same Called AET is used for Query and Retrieve
Port	FIXED	104
TLS-Secured Port	FIXED	2762
Send C-MOVE RSPs with Pending Status to the C-MOVE SCU during the retrieve process	FIXED	5 seconds
Remote Configuration Parameters - Query/Retrieve Service
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
Calling AE Title (SCU)	SERVICE
Called AE Title (SCP)	SERVICE
Port	SERVICE
TLS-Secured Port	SERVICE
Host	SERVICE

N.6.2.8 Print Management Service Configuration

Table N.6-9 lists Print Management Service configuration parameters:

Table N.6-9. Print Management Service Parameters

Local Configuration Parameters - Print Management Service
Parameter	Configurable	Default Value	Comments
[This example shows the configuration for a Print SCU, e.g., a modality.]	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
Calling AE Title (SCU)	FIXED	PRINT_AE
Remote Configuration Parameters - Print Management Service
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
Called AE Title (SCP)	SERVICE
Port	SERVICE	104
Host	SERVICE
printer template	SERVICE		A pre-defined printer template can be selected in a drop down list. Select "generic" if the printer template does not exist
Film sizes supported by the Print SCP	USER	All film sizes available	Select the film sizes which are relevant for the connected printer

N.6.3 Configuration of DICOM Web Services

The tables in the following subsections show the configuration parameters required for DICOM Web Services.

To identify whether <product> is an origin server and/or a user agent, the following applies:

Origin server: The (Secured) Local <Transaction Name> URL is present at the local configuration parameters.
User agent: The (Secured) Remote <Transaction Name> URL is present at the Remote configuration parameters.

["Local Configuration Parameters" describes parameters for the product described in this DCS, whereas "Remote Configuration Parameters" describes the information needed for this product to interface with a remote system. Remove rows for any unsupported parameters]

N.6.3.1 URI Web Service Configuration

Table N.6-10 lists the configuration parameters required for URI Web Service.

[Remove the unsupported parameters from the local and remote configuration parameters.]

Table N.6-10. URI Web Service Parameters

Local Configuration Parameters - URI Web Service
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
Local Retrieve Imaging Doc Set URL (Base URI)	FIXED	http://<Localhost>:<port>/wado/
Port	FIXED	8080
Secured Local Retrieve Imaging Doc Set URL (Base URI)	FIXED	https://<Localhost>:<Securedport>/wado/
Secured Port	FIXED	8081
<Specific URI web service parameter>
Remote Configuration Parameters - URI Web Service
[Either document the number of supported remote hosts, e.g <Product> supports configuration of up to <X> remote hosts, or state that there is no limitation other than the ones mandated by the operating system.].
Parameter	Configurable	Default	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank]	[Provide comments or Values/ranges if applicable]
Remote Retrieve Imaging Doc Set URL	SERVICE
Port	SERVICE
Secured Remote Retrieve Imaging Doc Set URL	SERVICE
Secured Port	SERVICE
<Specific URI web service parameter>

N.6.3.2 Studies Web Service Configuration

N.6.3.2.1 Retrieve Transaction (WADO-RS) Configuration

The Retrieve Transaction is also known as WADO-RS. Table N.6-11 lists configuration parameters for the Retrieve Transaction of the Studies Web Service:

[Remove the unsupported parameters from the local and remote configuration parameters.]

Table N.6-11. Retrieve Transaction Parameters

Local Configuration Parameters - Retrieve Transaction
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
Local Retrieve Imaging Doc Set URL (Base URI)	FIXED	https://<Localhost>:<port>/wado/
port	SERVICE	8081
Secured Local Retrieve Imaging Doc Set URL (Base URI)	FIXED	https://<Localhost>:<Securedport>/wado/
Secured Port	SERVICE
<Specific Retrieve Transaction parameter>
Remote Configuration Parameters - Retrieve Transaction
[Either document the number of supported remote hosts, e.g <Product> supports configuration of up to <X> remote hosts, or state that there is no limitation other than the ones mandated by the operating system.]
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank]	[Provide comments or Values/ranges if applicable]
Remote Retrieve Imaging Doc Set URL	SERVICE
Port	SERVICE
Secured Remote Retrieve Imaging Doc Set URL	SERVICE
Secured Port	SERVICE
<Specific Retrieve Transaction parameter>

N.6.3.2.2 Store Transaction (STOW-RS) Configuration

The Store Transaction is also known as STOW-RS. Table N.6-12 lists configuration parameters for the Store Transaction of the Studies Web Service:

[Remove the unsupported parameters from the local and remote configuration parameters.]

Table N.6-12. Store Transaction Parameters

Local Configuration Parameters - Store Transaction
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank]	[Provide comments or Values/ranges if applicable]
Store local Origin Server URL (Base URI)	FIXED	http://<hostname>:<port>/stow
Port	SERVICE	8081
Secured Store local Origin Server URL (Base URI)	SERVICE
Secured Port	SERVICE
<Specific Store Transaction parameter>
Remote Configuration Parameters - Store Transaction
[Either document the number of supported remote hosts, e.g <Product> supports configuration of up to <X> remote hosts, or state that there is no limitation other than the ones mandated by the operating system.]
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank]	[Provide comments or Values/ranges if applicable]
Store remote Origin Server URL	USER
Port	USER
Secured Store Remote Origin Server URL	SERVICE
Secured Port	SERVICE
<Specific Store Transaction parameter>

N.6.3.2.3 Search Transaction (QIDO-RS) Configuration

The Search Transaction service is also known as QIDO-RS. Table N.6-13 lists configuration parameters for the Search Transaction of the Studies Web Service:

[Remove the unsupported parameters from the local and remote configuration parameters.]

Table N.6-13. Search Transaction Parameters

Local Configuration Parameters - Search Transaction
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank]	[Provide comments or Values/ranges if applicable]
Search local Origin Server URL (Base URI)	FIXED	http://<hostname>:<port>/qido
Port	SERVICE	8081
Secured Search local Origin Server URL (Base URI)		https://<hostname>:<securedport>/qido
Secured Port		8081
<Specific Search Transaction parameter>
Remote Configuration Parameters - Search Transaction
[Either document the number of supported remote hosts, e.g., <Product> supports configuration of up to <X> remote hosts, or state that there is no limitation other than those mandated by the operating system.]
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank]	[Provide comments or Values/ranges if applicable]
Search remote Origin Server URL	SERVICE
Port	SERVICE
Secured Search remote Origin Server URL	SERVICE
Secured Port	SERVICE
<Specific Search Transaction parameter>

N.6.3.3 Worklist Web Service Configuration

The Worklist Web Service is also known as UPS-RS.

Table N.6-14 lists the configuration parameters for the Worklist Web Service.

[Remove the unsupported parameters from the local and remote configuration parameters.]

Table N.6-14. Worklist Web Service Parameters

Local Configuration Parameters - Worklist Web Service
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
Worklist local Origin Server URL (Base URI)	FIXED	http://<hostname>:<port>/UPS
Port	SERVICE	8081
Secured Worklist local Origin Server URL (Base URI)	FIXED	https://<hostname>:<securedport>/UPS
Secured Port	SERVICE	8081
<Specific Worklist parameter>
Remote Configuration Parameters - Worklist Web Service
[Either document the number of supported remote hosts, e.g., <Product> supports configuration of up to <X> remote hosts, or state that there is no limitation other than the ones mandated by the operating system.]
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable]
Worklist remote Origin Server URL	SERVICE
Port	SERVICE
Secured Worklist remote Origin Server URL	SERVICE
Secured Port	SERVICE
<Specific Worklist parameter>

N.6.3.4 Non-Patient Instances (NPI) Web Service Configuration

Table N.6-15 lists the configuration parameters for the NPI Web Service.

[ Remove the unsupported parameters from the local and remote configuration parameters.]

Table N.6-15. NPI Web Service Parameters

Local Configuration Parameters - NPI Web Service
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
NPI local Origin Server URL (Base URI)	SERVICE	http://<hostname>:8081/NPI
Port	FIXED	8081
<Specific NPI web service parameter>
Remote Configuration Parameters - NPI Web Service
[Either document the number of supported remote hosts, e.g., <Product> supports configuration of up to <X> remote hosts, or state that there is no limitation other than the ones mandated by the operating system.]
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
NPI remote Origin Server URL	SERVICE
Port	SERVICE
Secured NPI remote Origin Server URL	SERVICE
Secured Port	SERVICE
<Specific NPI web service parameter>

N.6.3.5 Storage Commitment Service Configuration

N.6.3.5.1 Request Transaction Configuration

Table N.6.3.5-1 lists configuration parameters for the Request Transaction of the Storage Commitment Service:

[Remove the unsupported parameters from the local and remote configuration parameters.]

Table N.6.3.5-1. Request and Result Check Transaction Parameters

Local Configuration Parameters - Request and Result Check Transaction
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank]	[Provide comments or Values/ranges if applicable]
Commit local Origin Server URL (Base URI)	FIXED	http://<hostname>:<port>/commitment-requests
Port	SERVICE	8081
Secured Commit local Origin Server URL (Base URI)	SERVICE
Secured Port	SERVICE
Result Availability Duration	FIXED	24	The number of hours that the storage commitment request result is guaranteed to be retrievable from the origin server.
<Specific Storage Commitment Service parameter>
Remote Configuration Parameters - Request and Result Check Transaction
[Either document the number of supported remote hosts, e.g <Product> supports configuration of up to <X> remote hosts or state that there is no limitation other than the ones mandated by the operating system.]
Parameter	Configurable	Default Value	<emphasis role="bold">
	<<USER SERVICE FIXED>>	[If there is no default, leave blank]	[Provide comments or Values/ranges if applicable]
Commit remote Origin Server URL	USER
Port	USER
Secured Commit Remote Origin Server URL	SERVICE
Secured Port	SERVICE
Result Availability Duration	FIXED	24	The number of hours that the storage commitment request result is guaranteed to be retrievable from the origin server.
<Specific Storage Commitment Service parameter>

N.6.3.5.2 Result Check Transaction Configuration

Table N.6.3.5-1 lists configuration parameters for the Result Check Transaction of the Storage Commitment Service.

N.6.4 Configuration of Media Storage Service

Table N.6-16 lists configuration parameters for the Media Storage service.

Table N.6-16. Media Storage Service Parameters

Local Configuration Parameters - Media Storage Service
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED>>	[If there is no default, leave blank.]	[Provide comments or Values/ranges if applicable.]
Source Application Entity Title	FIXED	MEDIA
<Specific Media Storage parameter>

N.6.5 Configuration of Real-Time Video Service

Table N.6-17 lists configuration parameters for the Real-Time Video service.

Table N.6-17. RTV Service Parameters

Local Configuration Parameters - RTV Service
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED N/A>>	[If there is no default, leave blank.]	[Optionally put a comment helping to understand the configuration/parameter, and list Value ranges if applicable.]
<specific Real-Time Video parameter>
Remote Configuration Parameters - RTV Service
[Either document the number of supported remote hosts, e.g., <Product> supports configuration of up to <X> remote hosts, or state that there is no limitation other than the ones mandated by the operating system.]
Parameter	Configurable	Default Value	Comments
<specific Real-Time Video parameter>

N.6.6 Configuration of Audit Trail - Syslog

[If your system is only an originator remove the Collector Parameters Table.]

[If your system is only a collector remove the Originator Parameters Table.]

[If your system is both an originator and a collector, keep both tables and indicate if it is a relay.]

Table N.6-18 lists configuration parameters for the Audit Trail Originator.

Table N.6-18. Audit Trail Originator Parameters

Originator Audit Trail Message Transmission - SYSLOG Parameters
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED N/A>>	[If there is no default, leave blank.]	[Optionally put in a comment helping a reader to understand the configuration/parameter, and list Value ranges if applicable.]
Remote Port number	SERVICE	514	Can configure multiple remote syslog repository
Remote secured port number	SERVICE	6514
Remote Host name/IP	SERVICE
UDP Protocol	N/A
TLS Protocol	FIXED	TLS	only TLS is supported
Maximum Size sent
<Specific Originator Audit Trail Message Transmission-SYSLOG parameters>

Table N.6-19 lists configuration parameters for the Audit Trail Collector.

Table N.6-19. Audit Trail Collector Parameters

Collector Audit Trail Message Transmission - SYSLOG Parameters
Parameter	Configurable	Default Value	Comments
	<<USER SERVICE FIXED N/A>>	[If there is no default, leave blank.]	[Optionally put a comment helping to understand the configuration/parameter, and list Value ranges if applicable.]
Local Listening Port Number	SERVICE	514
Local Listening Secured port number	FIXED	6514
Local Host Name/IP	SERVICE
UDP Protocol	N/A		UDP not supported
TLS Protocol	FIXED	TLS	only TLS is supported
Maximum Size Received
<Specific Collector Audit Trail Message Transmission-SYSLOG parameter>

N.7 Network and Media Communication Details

N.7.1 General

The cross interaction between the AEs is depicted in the diagrams below.

[Shown below are some examples of cross AE interactions. Modify them to match your product implementation.]

Figure N.7-1. Real-World Activity and Cross AE interaction

Figure N.7-2. Real-World Activity and Cross AE interaction - Query Retrieve

N.7.1.1 General Association Parameters

Table N.7-1 lists Association parameters applicable to all AEs on the system.

[If the Association parameters for your system are the same across all AEs, fill in the table below and mark the respective sections for AE specific Association parameters as N/A. If your system uses different Association parameters for each AE replace the content of this section with N/A and append N/A to the section heading.]

Table N.7-1. General Association Parameters

	Name	Value
Networking Services	Application Context Name	1.2.840.10008.3.1.1.1
	Implementation Class UID
	Implementation Version Name
	Maximum PDU Length	Default: 4096
	ARTIM Timeout	Default: 30s
	Maximum number of simultaneous Associations as Association Initiator
	Maximum number of simultaneous Associations as Association Acceptor
	Maximum number of outstanding asynchronous Transactions
Media Services	File Meta Information Version
	Implementation Class UID
	Implementation Version Name
Web Services	Maximum number of connections supported as Server
<Service Category>	<Parameter>	<Parameter Value>

N.7.2 Specifications

N.7.2.1 <AE1> Application Entity

N.7.2.1.1 Sequencing of Real-World Activities for <AE1>

Figure N.7-3. Sequencing of Real-World Activities for <AE1>

[Describe the messaging sequence of AE for a Real-World activity that is performed.

E.g.: Local Real-World Activity <2> first open an Association, triggers message <a> and message <b> on this Association before closing it. Action <c> is then performed on the system before Local Real-World Activity <1> can be launched to send message <d> on a new Association and receives message <e> on the same Association.]

[Also include its use of DICOM Web Services, including any proxy functionality between a Web Service and the equivalent DIMSE Service here.

Also include its use of DICOM-RTV Services, including any proxy functionality between a DICOM-RTV and another service provided through DIMSE Service or RESTful (i.e., storage of received video and audio with associated metadata).

Note

Note: This diagram may be split into multiple diagrams to represent each service separately.]

[Below are examples for a Query Retrieve AE and a Web AE. Modify as applicable for your product implementation.]

Figure N.7-4. Sequencing of Real-World Activities for <QueryRetrieve AE>

Figure N.7-5. Sequencing of Real-World Activities for <Web AE>

N.7.2.1.2 Association Parameters of <AE1>

Table N.7-2 lists Association parameters applicable to <AE1.>

[If your system uses different Association parameters for each AE fill in the table below for each AE and mark this section as N/A.]

Table N.7-2. Association Parameters for <AE1>

	Name	Value
Networking Services	Application Context Name	1.2.840.10008.3.1.1.1
	Implementation Class UID
	Implementation Version Name
	Maximum PDU Length	Default: 4096
	ARTIM Timeout	Default: 30s
	Maximum number of simultaneous Associations as Association Initiator
	Maximum number of simultaneous Associations as Association Acceptor
	Maximum number of outstanding asynchronous Transactions
Media Services	File Meta Information Version
	Implementation Class UID
	Implementation Version Name
Web Services	Maximum number of connections supported as Server
<Service Category>	<Parameter Name>	<Parameter Value>

N.7.2.1.3 Association Initiation

This section details the Association policies of the Application Entity when it is initiating an Association.

[For each Real-World Activity of AE1 provide subsections Section N.7.2.1.3, “Association Initiation”.x.]

N.7.2.1.3.1 Real-World Activity <Activity 1>

[Describe the policies for creating Associations. Include the following details:

Policy with respect to Presentation Context, e.g., a list of transfer syntaxes is proposed for a SOP class of the Storage service when the instances of the SOP class are available only in a certain transfer encoding.]

[For storage, specify

whether all instances are sent on the same Association or whether a new Association request is initiated for each instance.
The Association policy in case Transfer is triggered manually or when transfer occurs automatically (for instance based on C-MOVE)

]

[Describe the actions and behavior that cause the product to issue N-ACTION requests and how it relates to the previous storage request, e.g., is the storage commitment initiated right after a successful C-STORE, or is the storage commitment issued after all instance in the study have been successfully stored, …]

[Describe the Association initiation behavior of your product with regards to the N-EVENT-REPORT request, e.g., whether the N-EVENT-REPORT request is sent on the same Association or whether it is initiated on a different Association.]

[Describe your system behavior if your product cannot establish an Association with the SCU, e.g., is there a retry mechanism, is that configurable, …]

Extended Negotiation

The Extended Negotiation parameters for all services that are supported by the Application Entity for the Real-World Activity <Activity 1> are described in Table N.7-3.

[Describe below all the Extended Negotiation that the Application Entity requests for the <Activity 1> during Association negotiation. Use "Y" in the "Support" column to indicate support for Extended Negotiation or "N" to indicate that Extended Negotiation is not supported, and the default Value is sent in the Association field. Describe any behavior pertaining to handling extended behavior during Association initiation under this section.]

[Modify the table below to reflect the services participating in <Activity 1>.]

Table N.7-3. Extended Negotiation for <Activity 1> of <AE1> - Association Initiation

SOP Class	Extended Negotiation	Requested Value
Modality Worklist
Modality Worklist Information Model - FIND	Fuzzy semantic matching of person names	<0,1>
Modality Worklist Information Model - FIND	Timezone query adjustment	<0,1>
Storage
Applicable to all Storage SOP Classes listed under Section N.5.	Level of support	<3>
	Level of Digital Signature support	<(0) ,1,2,3>
	Element Coercion	<0,1,(2) >
Query
Applicable to all Query Retrieve - FIND SOP Classes mentioned under Section N.5.	Relational queries	<0,1>
	Date-time matching	<0,1>
	Fuzzy semantic matching of person names	<0,1>
	Timezone query adjustment	<0,1>
	Enhanced Multi-Frame Image Conversion	<0,1>
Retrieve
Applicable to all Query Retrieve - MOVE SOP Classes mentioned under Section N.5.	Relational retrieval	<0,1>
	Enhanced Multi-Frame Image Conversion	<0,1>
	Timezone query adjustment	1
Unified Worklist and Procedure Step
Unified Worklist and Procedure Step	Fuzzy semantic matching of person names	<0,1>
Unified Worklist and Procedure Step	Timezone query adjustment	<0,1>

Role Negotiation

[Describe if the AE supports Role Negotiation in the case of Storage commitment happening synchronously i.e., if the N-ACTION and the N-EVENT-REPORT are performed in the same Association.]

N.7.2.1.4 Association Acceptance

This section details the Association policies of the Application Entity when it is the acceptor of an Association.

[For each Real-World Activity of AE1 provide subsections Section N.7.2.1.4, “Association Acceptance”.x.]

N.7.2.1.4.1 Real-World Activity <Activity 2>

[Describe the service specific Association acceptance behavior of your product, e.g.

For storage commitment describe whether an N-EVENT-REPORT request is expected on the same Association or whether it is expected on a different Association.]

Extended Negotiation

The Extended Negotiation parameters for all services that are requested by the Application Entity for the Real-World Activity <Activity 2> are described in Table N.7-4.

[Describe below all the Extended Negotiation that the Application Entity supports for <Activity 2> during Association negotiation. Use "Y" in the "Support" column to indicate support for Extended Negotiation or "N" to indicate that Extended Negotiation is not supported, and the default Value is sent in the Association field. Describe any behavior pertaining to handling extended behavior during Association acceptance under this section.]

[Modify the table below to reflect the services participating in <Activity 2>.]

Table N.7-4. Extended Negotiation for <Activity 2> of <AE1> - Association Acceptance

SOP Class	Extended Negotiation	Requested Value
Modality Worklist
Modality Worklist Information Model - FIND (1.2.840.10008.5.1.4.31)	Fuzzy semantic matching of person names	<0,1>
	Timezone query adjustment	<0,1>
Storage
Applicable to all Storage SOP Classes listed under Section N.5.	Level of support	<0,1,2,(3) >
	Level of Digital Signature support	<(0) ,1,2,3>
	Element Coercion	<0,1,(2) >
Query
Applicable to all Query Retrieve - FIND SOP Classes mentioned under Section N.5.	Relational queries	<0,1>
	Date-time matching	<0,1>
	Fuzzy semantic matching of person names	<0,1>
	Timezone query adjustment	<0,1>
	Enhanced Multi-Frame Image Conversion	<0,1>
Retrieve
Applicable to all Query Retrieve - MOVE SOP Classes mentioned under Section N.5.	Relational retrieval	<0,1>
	Enhanced Multi-Frame Image Conversion	<0,1>
	Timezone query adjustment	<1>
Unified Worklist and Procedure Step
Unified Worklist and Procedure Step	Fuzzy semantic matching of person names	<0,1>
Unified Worklist and Procedure Step	Timezone query adjustment	<0,1>

Transfer Syntax Selection Policies

This section provides tables that describe the Transfer Syntax preference for different SOP Classes or SOP Class groups when there are multiple Transfer Syntaxes provided by the Association initiator for Real-World Activity <Activity 2> of <AE1> of the system.

[The preference for Transfer Syntax selection is based on the type of data i.e., Image SOP Classes, Video SOP Classes or non-image/video SOP Classes.]

[Edit the tables below to indicate the transfer selection polices applicable to the documented activity.

If there are exceptions to the standard preference SOP Classes, mention this in the "Comments" column.

If the preference order is based on some other criteria, add another table.]

Table N.7-5. Transfer Syntax Selection Preference Order - Image SOP Classes for <AE1>

Preference Order	Transfer Syntax	UID
1	JPEG Lossless, Hierarchical, First-Order Prediction Transfer Syntax	1.2.840.10008.1.2.4.70
2	RLE Lossless	1.2.840.10008.1.2.5
3	Explicit VR Little-Endian Transfer Syntax	1.2.840.10008.1.2.1
4	Implicit VR Little-Endian Transfer Syntax	1.2.840.10008.1.2
5	Explicit VR Big-Endian Transfer Syntax	1.2.840.10008.1.2.2

Table N.7-6. Transfer Syntax Selection Preference Order - Video SOP Classes for <AE1>

Preference Order	Transfer Syntax	UID
1	MPEG2 Main Profile / Main Level	1.2.840.10008.1.2.4.100
2	MPEG-4 AVC/H.264 Stereo High Profile / Level 4.2	1.2.840.10008.1.2.4.106
3	Explicit VR Little-Endian Transfer Syntax	1.2.840.10008.1.2.1
4	Implicit VR Little-Endian Transfer Syntax	1.2.840.10008.1.2
5	Explicit VR Big-Endian Transfer Syntax	1.2.840.10008.1.2.2

Table N.7-7. Transfer Syntax Selection Preference Order - Non-Image SOP Classes for <AE1>

Preference Order	Transfer Syntax	UID
1	Explicit VR Little-Endian Transfer Syntax	1.2.840.10008.1.2.1
2	Implicit VR little-Endian Transfer Syntax	1.2.840.10008.1.2
3	Explicit VR Big-Endian Transfer Syntax	1.2.840.10008.1.2.2

N.7.3 Status Codes

The following sections describe the Status Codes supported by the system for each implemented service as well as the reason for issuing specific Status Codes or the associated behavior when receiving it.

[Throughout all SCP related subsections, if necessary provide in the "Condition" Column further information (beyond the information in the "Further Meaning" Column) on the specific situation/condition, in which the respective Status Code is sent. E.g. for the Status Code

"A700 - Refused: Out of Resource" document details whether there is no space in the database, or on the hard drive, …
"0110 Processing Failure" document the nature of the processing failure.]

N.7.3.1 General AE Communication and Failure Behavior and Handling

N.7.3.1.1 Communication Failure Behavior as Association Initiator

Table N.7-8 describes behavior of the AE if a communication failure occurs when it initiated an Association.

[Describe below the behavior of the AE if a communication failure occurs when it initiated an Association, e.g.: Timeout, Network disconnect ABORT etc.]

Table N.7-8. DICOM Communication Failure Behavior as Association Initiator

Failure

Failure Behavior

Timeout

[Describe what the Application Entity does, if it does not receive any messages after the Association request and times out, e.g.,]

The Association is aborted using A-ABORT and command marked as failed. The reason is logged and reported to the user.

Association aborted

[Describe what the Application Entity does if an ABORT happens during the Association, e.g.,]

The command is marked as failed. The reason is logged and reported to the user.

Network Disconnect

[Describe what an Application Entity does if the network is disconnected during Association, e.g.,]

The command is marked as failed. The reason is logged and reported to the user. Automatic retry of this service connection is started

N.7.3.1.2 Communication Failure Handling as Association Acceptor

Table N.7-9 describes how the AE responds when it receives an Association request that leads to a failure in communication.

[Describe how the AE responds when it receives Association requests that leads to a failure in communication: application error during processing, unrecognized PDU values in the Association request etc. List all cases supported by the product.]

Table N.7-9. DICOM Communication Failure Handling as Association Acceptor

Exception

Failure response

Failure during processing of an Association request

[Describe what the AE does if there is an internal error during processing of an Association request, e.g.,]

ABORT message is sent out and the connection is closed

Unrecognized Called AE

[Describe what the AE does if the Called AE is not recognized, e.g.,]

AE responds with Association-RJ

Exceed limit for number of connections supported

[Describe what the AE does if it receives a new Association request if the limit of connections supported by the AE is exceeded, e.g.,]

AE responds with Association-RJ

N.7.3.2 DIMSE Services

N.7.3.2.1 Basic Worklist Management Service

N.7.3.2.1.1 SCU of the Modality Worklist Information Model Find SOP Class - C-FIND

Table N.7-10 lists the Status Codes that the SCU of the Modality Worklist Information Model Find SOP Class supports for the C-FIND message and defines the application behavior when encountering the listed Status Codes.

[Describe the behavior of the application when it receives any of the Status Codes listed in the table below, e.g., displaying and logging the error code or retrying the request. For each additional Status Code supported add a row to the table.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-10. Status Codes for C-FIND of the Modality Worklist Information Model SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Matching is complete - No final identifier is supplied	0000
Failure	Refused: Out of Resources	A700
	SOP Class Not Supported	0122
	Error: Data Set does not match SOP Class	A900
	Error: Unable to process	C000-CFFF
Cancel	Matching terminated due to cancel	FE00
Pending	Matches are continuing - Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys.	FF00
	Matches are continuing - Warning that one or more Optional Keys were not supported for existence for this Identifier	FF01
-	Other Status Codes	anything else

N.7.3.2.1.2 SCP of the Modality Worklist Information Model Find SOP Class - C-FIND

Table N.7-11 lists the Status Codes that the SCP of the Modality Worklist Information Model Find SOP Class supports for the C-FIND message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-11. Status Codes for C-FIND of the Modality Worklist Information Model SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Matching is complete - No final identifier is supplied	0000
Failure	Refused: Out of Resources	A700
	SOP Class Not Supported	0122
	Error: Data Set does not match SOP Class	A900
	Error: Unable to process	C000-CFFF
Cancel	Matching terminated due to cancel	FE00
Pending	Matches are continuing - Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys.	FF00
	Matches are continuing - Warning that one or more Optional Keys were not supported for existence for this Identifier	FF01

N.7.3.2.2 Modality Performed Procedure Step Service

N.7.3.2.2.1 SCU of the Modality Performed Procedure Step SOP Class - N-CREATE

Table N.7-12 lists the Status Codes that the SCU of the Modality Performed Procedure Step SOP Class supports for the N-CREATE message and defines the application behavior when encountering the listed Status Codes.

[In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-12. Status Codes for N-CREATE of the Modality Performed Procedure Step SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Attribute Value out of range	0116
Warning	Attribute List warning	0107
Failure	No such Attribute	0105
	Invalid Attribute Value	0106
	Processing Failure	0110
	Duplicate SOP Instance	0111
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Missing Attribute	0120
	Missing Attribute Value	0121
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
-	Other Status Codes	anything else

N.7.3.2.2.2 SCU of the Modality Performed Procedure Step SOP Class - N-SET

Table N.7-13 lists the Status Codes that the SCU of the Modality Performed Procedure Step SOP Class supports for the N-SET message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-13. Status Codes for N-SET of the Modality Performed Procedure Step SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Attribute Value out of range	0116
Warning	Attribute List warning	0107
Failure	No such Attribute	0105
	Invalid Attribute Value	0106
	Processing Failure	0110
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class-Instance conflict	0119
	Missing Attribute Value	0121
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
-	Other Status Codes	anything else

N.7.3.2.2.3 SCP of the Modality Performed Procedure Step SOP Class - N-CREATE

Table N.7-14 lists the Status Codes that the SCP of the Modality Performed Procedure Step SOP Class supports for the N-CREATE message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-14. Status Codes for N-CREATE of the Modality Performed Procedure Step SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Attribute Value out of range	0116
Warning	Attribute List warning	0107
Failure	Duplicate invocation	0210
	Duplicate SOP Instance	0111
	Invalid Attribute Value	0106
	Invalid SOP Instance	0117
	Missing Attribute	0120
	Missing Attribute Value	0121
	Mistyped argument	0212
	No such Attribute	0105
	No such SOP Class	0118
	Processing Failure	0110
	Resource limitation	0213
	Unrecognized operation	0211
	Refused: Not authorized	0124

N.7.3.2.2.4 SCP of the Modality Performed Procedure Step SOP Class - N-SET

Table N.7-15 lists the Status Codes that the SCP of the Modality Performed Procedure Step SOP Class supports for the N-SET message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-15. Status Codes for N-SET of the Modality Performed Procedure Step SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Attribute Value out of range	0116
Warning	Attribute List warning	0107
Failure	No such Attribute	0105
	Invalid Attribute Value	0106
	Processing Failure	0110
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class-Instance conflict	0119
	Missing Attribute Value	0121
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213

N.7.3.2.3 Unified Worklist und Procedure Step Service

N.7.3.2.3.1 SCU of the UPS Push SOP Class

N.7.3.2.3.1.1 SCU of the UPS Push SOP Class - N-CREATE

Table N.7-16 lists the Status Codes that the SCU of the UPS Push SOP Class supports for the N-CREATE message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-16. Status Codes for N-CREATE of the UPS Push SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	The UPS was created as requested	0000
Warning	The UPS was created with modifications	B300
	Attribute Value out of range	0116
	Attribute List warning	0107
Failure	Duplicate invocation	0210
	No such Attribute	0105
	Invalid Attribute Value	0106
	Processing failure	0110
	Duplicate SOP Instance	0111
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Missing Attribute	0120
	Missing Attribute Value	0121
	Refused: Not authorized	0124
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
	Failed: The provided Value of UPS State was not "SCHEDULED".	C309
-	Other Status Codes	anything else

N.7.3.2.3.1.2 SCU of the UPS Push SOP Class Request UPS Cancel - N-ACTION

Table N.7-17 lists the Status Codes that the SCU of the Request UPS Cancel on UPS Push SOP Class supports for the N-ACTION message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-17. Status Codes for N-ACTION of the UPS Push SOP Class Request UPS Cancel - SCU

Service Status	Further Meaning	Status Code
Success	The cancel request is acknowledged	0000
Warning	The UPS is already in the requested state of CANCELED	B304
Failure	Class-instance conflict	0119
	Duplicate invocation	0210
	Invalid argument Value	0115
	Invalid SOP Instance	0117
	Mistyped argument	0212
	No such action	0123
	No such argument	0114
	No such SOP Class	0118
	No such SOP Instance	0112
	Processing failure	0110
	Resource limitation	0213
	Unrecognized operation	0211
	Refused: Not authorized	0124
	Failed: The UPS is already COMPLETED	C311
	Failed: Performer chooses not to cancel	C313
	Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP	C307
	Failed: The performer cannot be contacted	C312
-	Other Status Codes	anything else

N.7.3.2.3.1.3 SCU of the UPS Push SOP Class - N-GET

Table N.7-18 lists the Status Codes that the SCU of the UPS Push SOP Class supports for the N-GET message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-18. Status Codes for N-GET of the UPS Push SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Requested optional Attributes are not supported.	0001
Warning	Attribute List warning	0107
Failure	Class-instance conflict	0119
	Duplicate invocation	0210
	Mistyped argument	0212
	Invalid SOP Instance	0117
	No such SOP Class	0118
	No such SOP Instance	0112
	Processing failure	0110
	Resource limitation	0213
	Unrecognized operation	0211
	Refused: Not authorized	0124
	Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP	C307
-	Other Status Codes	anything else

N.7.3.2.3.2 SCU of the UPS Pull SOP Class

N.7.3.2.3.2.1 SCU of the UPS Pull SOP Class - C-FIND

Table N.7-19 lists the Status Codes that the SCU of the UPS Pull SOP Class supports for the C-FIND message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-19. Status Codes for C-FIND of the UPS Pull SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Matching is complete - No final identifier is supplied	0000
Failure	Refused: Out of Resources	A700
	Error: Data Set does not match SOP Class	A900
	Failed: Unable to process	C000-CFFF
	Failed: SOP Class Not Supported	0122
Cancel	Matching terminated due to cancel	FE00
Pending	Matches are continuing - Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys.	FF00
	Matches are continuing - Warning that one or more Optional Keys were not supported for existence for this Identifier	FF01
-	Other Status Codes	anything else

N.7.3.2.3.2.2 SCU of the UPS Pull SOP Class - N-GET

Table N.7-20 lists the Status Codes that the SCU of the UPS Pull SOP Class supports for the N-GET message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-20. Status Codes for N-GET of the UPS Pull SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Requested optional Attributes are not supported.	0001
	Attribute List warning	0107
Failure	Class-instance conflict	0119
	Duplicate invocation	0210
	Mistyped argument	0212
	Invalid SOP Instance	0117
	No such SOP Class	0118
	No such SOP Instance	0112
	Processing failure	0110
	Resource limitation	0213
	Unrecognized operation	0211
	Refused: Not authorized	0124
	Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP	C307
-	Other Status Codes	anything else

N.7.3.2.3.2.3 SCU of the UPS Pull SOP Class - N-SET

Table N.7-21 lists the Status Codes that the SCU of the UPS Pull SOP Class supports for the N-SET message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-21. Status Codes for N-SET of the UPS Pull SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Requested optional Attributes are not supported.	0001
	Coerced invalid Values to valid Values	B305
	Attribute Value out of range	0116
	Attribute List warning	0107
Failure	Class-instance conflict	0119
	Duplicate invocation	0210
	Invalid Attribute Value	0106
	Mistyped argument	0212
	Missing Attribute Value	0121
	No such Attribute	0105
	No such SOP Class	0118
	No such SOP Instance	0112
	Processing failure	0110
	Resource limitation	0213
	Unrecognized operation	0211
	Refused: Not authorized	0124
	Failed: The UPS is not in the "IN PROGRESS" state	C310
	Failed: The correct Transaction UID was not provided	C301
	Failed: The UPS may no longer be updated	C300
	Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP	C307
-	Other Status Codes	anything else

N.7.3.2.3.2.4 SCU of the Change UPS State of UPS Pull SOP Class - N-ACTION

Table N.7-22 lists the Status Codes that the SCU of the Change UPS State of UPS Pull SOP Class supports for the N-ACTION message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-22. Status Codes for N-ACTION of the UPS Pull SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	The requested state change was performed	0000
Warning	The UPS is already in the requested state of CANCELED	B304
	The UPS is already in the requested state of COMPLETED	B306
Failure	Class-instance conflict	0119
	Duplicate invocation	0210
	Invalid argument Value	0115
	Invalid SOP Instance	0117
	Mistyped argument	0212
	No such action	0123
	No such argument	0114
	No such SOP Class	0118
	No such SOP Instance	0112
	Processing failure	0110
	Resource limitation	0213
	Unrecognized operation	0211
	Refused: Not authorized	0124
	Failed: The UPS may no longer be updated	C300
	Failed: The correct Transaction UID was not provided	C301
	Failed: The UPS is already IN PROGRESS	C302
	Failed: The UPS may only become SCHEDULED via N-CREATE, not N-SET or N-ACTION	C303
	Failed: The UPS has not met final state requirements for the requested state change	C304
	Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP	C307
	Failed: The UPS is not yet in the "IN PROGRESS" state	C310
-	Other Status Codes	anything else

N.7.3.2.3.3 SCU of the UPS Watch SOP Class

N.7.3.2.3.3.1 SCU of the Un/Subscribe on UPS Watch SOP Class - N-ACTION

Table N.7-23 lists the Status Codes that the SCU of the Un/Subscribe of the UPS Watch SOP Class supports for the N-ACTION message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-23. Status Codes for N-ACTION (Subscribe/Unsubscribe) of the UPS Watch SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	The requested change of subscription state was performed	0000
Warning	Deletion Lock not granted.	B301
Failure	Class-instance conflict	0119
	Duplicate invocation	0210
	Invalid argument Value	0115
	Invalid SOP Instance	0117
	Mistyped argument	0212
	No such action	0123
	No such argument	0114
	No such SOP Class	0118
	No such SOP Instance	0112
	Processing failure	0110
	Resource limitation	0213
	Unrecognized operation	0211
	Refused: Not authorized	0124
	Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP	C307
	Failed: Receiving AE-TITLE is Unknown to this SCP	C308
	Failed: Specified action not appropriate for specified instance	C314
	Failed: SCP does not support Event Reports	C315
-	Other Status Codes	anything else

N.7.3.2.3.3.2 SCU of the UPS Watch SOP Class - N-GET

Table N.7-24 lists the Status Codes that the SCU of the UPS Watch SOP Class supports for the N-GET message and defines the application behavior when encountering any the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-24. Status Codes for N-GET of the UPS Watch SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Requested optional Attributes are not supported.	0001
	Attribute List warning	0107
Failure	Class-instance conflict	0119
	Duplicate invocation	0210
	Mistyped argument	0212
	Invalid SOP Instance	0117
	No such SOP Class	0118
	No such SOP Instance	0112
	Processing failure	0110
	Resource limitation	0213
	Unrecognized operation	0211
	Refused: Not authorized	0124
	Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP	C307
-	Other Status Codes	anything else

N.7.3.2.3.3.3 SCU of the UPS Watch SOP Class - C-FIND

Table N.7-25 lists the Status Codes that the SCU of the UPS Watch SOP Class supports for the C-FIND message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-25. Status Codes for C-FIND of the UPS Watch SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Matching is complete - No final identifier is supplied	0000
Failure	Refused: Out of Resources	A700
	Error: Data Set does not match SOP Class	A900
	Failed: Unable to process	C000-CFFF
	Failed: SOP Class Not Supported	0122
Cancel	Matching terminated due to cancel	FE00
Pending	Matches are continuing - Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys.	FF00
	Matches are continuing - Warning that one or more Optional Keys were not supported for existence for this Identifier	FF01
-	Other Status Codes	anything else

N.7.3.2.3.3.4 SCU of the Request UPS Cancellation on UPS Watch SOP Class - N-ACTION

Table N.7-26 lists the Status Codes that the SCU of the Request UPS Cancellation on UPS Watch SOP Class supports for the C-ACTION message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-26. Status Codes for N-ACTION (Request Cancel) of the UPS Watch SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	The cancel request is acknowledged	0000
Warning	The UPS is already in the requested state of CANCELED	B304
Failure	Class-instance conflict	0119
	Duplicate invocation	0210
	Invalid argument Value	0115
	Invalid SOP Instance	0117
	Mistyped argument	0212
	No such action	0123
	No such argument	0114
	No such SOP Class	0118
	No such SOP Instance	0112
	Processing failure	0110
	Resource limitation	0213
	Unrecognized operation	0211
	Refused: Not authorized	0124
	Failed: The UPS is already COMPLETED	C311
	Failed: Performer chooses not to cancel	C313
	Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP	C307
	Failed: The performer cannot be contacted	C312
-	Other Status Codes	anything else

N.7.3.2.3.4 SCU of the UPS Event SOP Class

N.7.3.2.3.4.1 SCU of the UPS Event SOP Class - N-EVENT-REPORT

Table N.7-27 lists the Status Codes that the SCU of the UPS Event SOP Class supports for the N-EVENT-REPORT message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-27. Status Codes for the N-EVENT-REPORT of the UPS Event SOP Class - SCU

Service Status	Further Meaning	Status Code
Success		0000
Failure	Class-instance conflict	0119
	Duplicate invocation	0210
	Invalid argument Value	0115
	Invalid SOP Instance	0117
	Mistyped argument	0212
	No such event type	0113
	No such argument	0114
	No such SOP Class	0118
	No such SOP Instance	0112
	Processing failure	0110
	Resource limitation	0213
	Unrecognized operation	0211
-	Other Status Codes	anything else

N.7.3.2.3.5 SCP of the UPS Push SOP Class

N.7.3.2.3.5.1 SCP of the UPS Push SOP Class - N-CREATE

Table N.7-28 lists the Status Codes that the SCP of the UPS Push SOP Class supports for the N-CREATE message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-28. Status Codes for N-CREATE of the UPS Push SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	The UPS was created as requested	0000
Warning	The UPS was created with modifications	B300
	Attribute Value out of range	0116
	Attribute List warning	0107
Failure	Duplicate invocation	0210
	Duplicate SOP Instance	0111
	Invalid Attribute Value	0106
	Invalid SOP Instance	0117
	Missing Attribute	0120
	Missing Attribute Value	0121
	Mistyped argument	0212
	No such Attribute	0105
	No such SOP Class	0118
	Processing failure	0110
	Resource limitation	0213
	Unrecognized operation	0211
	Refused: Not authorized	0124
	Failed: The provided Value of UPS State was not "SCHEDULED".	C309

N.7.3.2.3.5.2 SCP of Request UPS Cancel on UPS Push SOP Class - N-ACTION

Table N.7-29 lists the Status Codes that the SCP of the UPS Push SOP Class supports for the N-ACTION message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-29. Status Codes for N-ACTION (Request Cancel) of the UPS Push SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	The cancel request is acknowledged	0000
Warning	The UPS is already in the requested state of CANCELED	B304
Failure	Class-instance conflict	0119
	Duplicate invocation	0210
	Invalid argument Value	0115
	Invalid SOP Instance	0117
	Mistyped argument	0212
	No such action	0123
	No such argument	0114
	No such SOP Class	0118
	No such SOP Instance	0112
	Processing failure	0110
	Resource limitation	0213
	Unrecognized operation	0211
	Refused: Not authorized	0124
	Failed: The UPS is already COMPLETED	C311
	Failed: Performer chooses not to cancel	C313
	Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP	C307
	Failed: The performer cannot be contacted	C312

N.7.3.2.3.5.3 SCP of the UPS Push SOP Class - N-GET

Table N.7-30 lists the Status Codes that the SCP of the UPS Push SOP Class supports for the N-GET message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-30. Status Codes for N-GET of the UPS Push SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Requested optional Attributes are not supported.	0001
Warning	Attribute List warning	0107
Failure	Class-instance conflict	0119
	Duplicate invocation	0210
	Mistyped argument	0212
	Invalid SOP Instance	0117
	No such SOP Class	0118
	No such SOP Instance	0112
	Processing failure	0110
	Resource limitation	0213
	Unrecognized operation	0211
	Refused: Not authorized	0124
	Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP	C307

N.7.3.2.3.6 SCP of the UPS Pull SOP Class

N.7.3.2.3.6.1 SCP of the UPS Pull SOP Class - C-FIND

Table N.7-31 lists the Status Codes that the SCP of the UPS Pull SOP Class supports for the C-FIND message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-31. Status Codes C-FIND of the UPS Pull SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Matching is complete - No final identifier is supplied	0000
Cancel	Matching terminated due to cancel	FE00
Failure	Refused: Out of Resources	A700
	Error: Data Set does not match SOP Class	A900
	Failed: Unable to process	C000-CFFF
	Failed: SOP Class Not Supported	0122
Pending	Matches are continuing - Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys.	FF00
	Matches are continuing - Warning that one or more Optional Keys were not supported for existence for this Identifier	FF01

N.7.3.2.3.6.2 SCP of the UPS Pull SOP Class - N-GET

Table N.7-32 lists the Status Codes that the SCP of the UPS Pull SOP Class supports for the N-GET message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-32. Status Codes for N-GET of the UPS Pull SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Requested optional Attributes are not supported.	0001
Warning	Attribute List warning	0107
Failure	Class-instance conflict	0119
	Duplicate invocation	0210
	Mistyped argument	0212
	Invalid SOP Instance	0117
	No such SOP Class	0118
	No such SOP Instance	0112
	Processing failure	0110
	Resource limitation	0213
	Unrecognized operation	0211
	Refused: Not authorized	0124
	Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP	C307

N.7.3.2.3.6.3 SCP of the UPS Pull SOP Class - N-SET

Table N.7-33 lists the Status Codes that the SCP of the UPS Pull SOP Class supports for the N-SET message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-33. Status Codes for N-SET of the UPS Pull SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Requested optional Attributes are not supported.	0001
	Attribute Value out of range	0116
	Attribute List warning	0107
	Coerced invalid Values to valid Values	B305
Failure	Class-instance conflict	0119
	Duplicate invocation	0210
	Invalid Attribute Value	0106
	Mistyped argument	0212
	Invalid SOP Instance	0117
	Missing Attribute Value	0121
	No such Attribute	0105
	No such SOP Class	0118
	No such SOP Instance	0112
	Processing failure	0110
	Resource limitation	0213
	Unrecognized operation	0211
	Refused: Not authorized	0124
	Failed: The UPS is not in the "IN PROGRESS" state	C310
	Failed: The correct Transaction UID was not provided	C301
	Failed: The UPS may no longer be updated	C300
	Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP	C307

N.7.3.2.3.6.4 SCP of the Change UPS State of UPS Pull SOP Class - N-ACTION

Table N.7-34 lists the Status Codes that the SCP of the Change UPS State of the UPS Pull SOP Class supports for the N-ACTION message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-34. Status Codes for N-ACTION (change state) of the UPS Pull SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	The requested state change was performed	0000
Warning	The UPS is already in the requested state of CANCELED	B304
	The UPS is already in the requested state of COMPLETED	B306
Failure	Class-instance conflict	0119
	Duplicate invocation	0210
	Invalid argument Value	0115
	Invalid SOP Instance	0117
	Mistyped argument	0212
	No such action	0123
	No such argument	0114
	No such SOP Class	0118
	No such SOP Instance	0112
	Processing failure	0110
	Resource limitation	0213
	Unrecognized operation	0211
	Refused: Not authorized	0124
	Failed: The UPS may no longer be updated	C300
	Failed: The correct Transaction UID was not provided	C301
	Failed: The UPS is already IN PROGRESS	C302
	Failed: The UPS may only become SCHEDULED via N-CREATE, not N-SET or N-ACTION	C303
	Failed: The UPS has not met final state requirements for the requested state change	C304
	Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP	C307
	Failed: The UPS is not yet in the "IN PROGRESS" state	C310

N.7.3.2.3.7 SCP of the UPS Watch SOP Class

N.7.3.2.3.7.1 SCP of the Un/Subscribe on UPS Watch SOP Class - N-ACTION

Table N.7-35 lists the Status Codes that the SCP of the Un/Subscribe on the UPS Watch SOP Class supports for the N-ACTION message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-35. Status Codes for N-ACTION (Subscribe/Unsubscribe) of the UPS Watch SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	The requested change of subscription state was performed	0000
Warning	Deletion Lock not granted.	B301
Failure	Class-instance conflict	0119
	Duplicate invocation	0210
	Invalid argument Value	0115
	Invalid SOP Instance	0117
	Mistyped argument	0212
	No such action	0123
	No such argument	0114
	No such SOP Class	0118
	No such SOP Instance	0112
	Processing failure	0110
	Resource limitation	0213
	Unrecognized operation	0211
	Refused: Not authorized	0124
	Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP	C307
	Failed: Receiving AE-TITLE is Unknown to this SCP	C308
	Failed: Specified action not appropriate for specified instance	C314
	Failed: SCP does not support Event Reports	C315

N.7.3.2.3.7.2 SCP of the UPS Watch SOP Class - N-GET

Table N.7-36 lists the Status Codes that the SCP of the UPS Watch SOP Class supports for the N-GET message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-36. Status Codes for N-GET of the UPS Watch SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Requested optional Attributes are not supported.	0001
Warning	Attribute List warning	0107
Failure	Class-instance conflict	0119
	Duplicate invocation	0210
	Mistyped argument	0212
	Invalid SOP Instance	0117
	No such SOP Class	0118
	No such SOP Instance	0112
	Processing failure	0110
	Resource limitation	0213
	Unrecognized operation	0211
	Refused: Not authorized	0124
	Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP	C307

N.7.3.2.3.7.3 SCP of the UPS Watch SOP Class - C-FIND

Table N.7-37 lists the Status Codes that the SCP of the UPS Watch SOP Class supports for the C-FIND message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-37. Status Codes C-FIND of the UPS Watch SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Matching is complete - No final identifier is supplied	0000
Failure	Refused: Out of Resources	A700
	Error: Data Set does not match SOP Class	A900
	Failed: Unable to process	C000-CFFF
	Failed: SOP Class Not Supported	0122
Cancel	Matching terminated due to cancel	FE00
Pending	Matches are continuing - Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys.	FF00
	Matches are continuing - Warning that one or more Optional Keys were not supported for existence for this Identifier	FF01

N.7.3.2.3.7.4 SCP of the Request UPS Cancellation on UPS Watch SOP Class - N-ACTION

Table N.7-38 lists the Status Codes that the SCP of the Request UPS Cancellation on UPS Watch SOP Class supports for the N-ACTION message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-38. Status Codes for N-ACTION (Request Cancel) of the UPS Watch SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	The cancel request is acknowledged	0000
Warning	The UPS is already in the requested state of CANCELED	B304
Failure	Class-instance conflict	0119
	Duplicate invocation	0210
	Invalid argument Value	0115
	Invalid SOP Instance	0117
	Mistyped argument	0212
	No such action	0123
	No such argument	0114
	No such SOP Class	0118
	No such SOP Instance	0112
	Processing failure	0110
	Resource limitation	0213
	Unrecognized operation	0211
	Refused: Not authorized	0124
	Failed: The UPS is already COMPLETED	C311
	Failed: Performer chooses not to cancel	C313
	Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP	C307
	Failed: The performer cannot be contacted	C312

N.7.3.2.3.8 SCP of the UPS Event SOP Class

N.7.3.2.3.8.1 SCP of the UPS Event SOP Class - N-EVENT-REPORT

Table N.7-39 lists the Status Codes that the SCP of the UPS Event SOP Class supports for the N-EVENT-REPORT message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-39. Status Codes for N-EVENT-REPORT of the UPS Event SOP Class - SCP

Service Status	Further Meaning	Status Code
Success		0000
Warning	Attribute Value out of range	0116
Warning	Attribute List warning	0107
Failure	Class-instance conflict	0119
	Duplicate invocation	0210
	Invalid argument Value	0115
	Invalid SOP Instance	0117
	Mistyped argument	0212
	No such event type	0113
	No such argument	0114
	No such SOP Class	0118
	No such SOP Instance	0112
	Processing failure	0110
	Resource limitation	0213
	Unrecognized operation	0211

N.7.3.2.4 Instance Availability Notification Service

N.7.3.2.4.1 SCU of the Instance Availability Notification SOP Class - N-CREATE

Table N.7-40 lists the Status Codes that the SCU of the Instance Availability Notification SOP Class supports for the N-CREATE message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-40. Status Codes for N-CREATE for the Instance Availability Notification SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Attribute List warning	0107
Failure	No such Attribute	0105
	Invalid Attribute Value	0106
	Processing failure	0110
	Duplicate SOP Instance	0111
	Attribute Value out of range	0116
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Missing Attribute	0120
	Missing Attribute Value	0121
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
-	Other Status Codes	anything else

N.7.3.2.4.2 SCP of the Instance Availability Notification SOP Class - N-CREATE

Table N.7-41 lists the Status Codes that the SCP of the Instance Availability Notification SOP Class supports for the N-CREATE message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-41. Status Codes for N-CREATE for the Instance Availability Notification SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Failure	Class-instance conflict	0119
	Duplicate invocation	0210
	Duplicate SOP Instance	0111
	Invalid Attribute Value	0106
	Invalid SOP Instance	0117
	Missing Attribute	0120
	Missing Attribute Value	0121
	Mistyped argument	0212
	No such Attribute	0105
	No such SOP Class	0118
	No such SOP Instance	0112
	Processing failure	0110
	Resource limitation	0213
	Unrecognized operation	0211

N.7.3.2.5 Storage Service

N.7.3.2.5.1 SCU of the Storage SOP Classes - C-STORE

Table N.7-42 lists the Status Codes that the SCU of the Storage SOP Class supports for the C-STORE message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-42. Status Codes C-STORE for the Storage SOP Classes - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Coercion of Data Elements	B000
	Data Set does not match SOP Class	B007
	Elements Discarded	B006
Failure	SOP Class not supported	0112
	Invalid SOP Instance	0117
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Not authorized	0214
	Out of Resources	A700-A7FF
	Data Set does not match SOP Class	A900-A9FF
	Cannot Understand	C000-CFFF
-	Other Status Codes	anything else

N.7.3.2.5.2 SCP of the Storage SOP Classes - C-STORE

Table N.7-43 lists the Status Codes that the SCP of the Storage SOP Classes supports for the C-STORE message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

[List the Attributes that are used to further detail the Status Codes in the "Related Fields Columns". Use N/A if there are no related fields used.Further comments regarding the Related Fields can be provided in the "Condition" Column]

Table N.7-43. Status Codes C-STORE of the Storage SOP Classes - SCP

Service Status	Further Meaning	Status Codes
Success	Success	0000
Warning	Coercion of Data Elements	B000
	Data Set does not match SOP Class	B007
	Elements Discarded	B006
Refused	Refused: Out of Resources	A700
Failure	Error: Data Set does not match SOP Class	A901
Failure	Error: Cannot understand	C000

N.7.3.2.6 Storage Commitment Service

N.7.3.2.6.1 SCU of the Storage Commitment Push Model SOP Class - N-ACTION

Table N.7-44 lists the Status Codes that the SCU of the Storage Commitment Push Model SOP Class supports for the N-ACTION message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-44. Status Codes for N-ACTION of the Storage Commitment Push Model SOP Class - SCU

Service Status	Further Meaning	Status Code
Success		0000
Failure	Processing failure	0110
	No such SOP Instance	0112
	No such argument	0114
	Invalid argument Value	0115
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class-instance conflict	0119
	No such action	0123
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
-	Other Status Codes	anything else

N.7.3.2.6.2 SCU of the Storage Commitment Push Model SOP Class - N-EVENT-REPORT

Table N.7-45 lists the Status Codes that the SCU of the Storage Commitment Push Model SOP Class supports for the N-EVENT-REPORT message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-45. Status Codes for N-EVENT-REPORT for the Storage Commitment Push Model SOP Class - SCU

Service Status	Further Meaning	Status Code
Success		0000
Failure	Processing failure	0110
	No such SOP Instance	0112
	No such argument	0114
	Invalid argument Value	0115
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class-instance conflict	0119
	No such action	0123
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
-	Other Status Codes	anything else

N.7.3.2.6.3 SCP of the Storage Commitment Push Model SOP Class - N-ACTION

Table N.7-46 lists the Status Codes that the SCP of the Storage Commitment Push Model SOP Class supports for the N-ACTION message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-46. Status Codes for N-ACTION for the Storage Commitment Push Model SOP Class - SCP

Service Status	Further Meaning	Status Code
Success		0000
Failure	Processing failure	0110
	No such SOP Instance	0112
	No such argument	0114
	Invalid argument Value	0115
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class-instance conflict	0119
	No such action	0123
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213

N.7.3.2.6.4 SCP of the Storage Commitment Push Model SOP Class - N-EVENT-REPORT

Table N.7-47 lists the Status Codes that the SCP of the Storage Commitment Push Model SOP Class supports for the N-EVENT-REPORT message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-47. Status Codes for N-EVENT-REPORT for the Storage Commitment Push Model SOP Class - SCP

Service Status	Further Meaning	Status Code
Success		0000
Failure	Processing failure	0110
	No such SOP Instance	0112
	No such event type	0113
	No such argument	0114
	Invalid argument Value	0115
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class-instance conflict	0119
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
-	Other Status Codes	anything else

N.7.3.2.7 Query/Retrieve Service

N.7.3.2.7.1 SCU of the Query/Retrieve FIND SOP Classes - C-FIND

Table N.7-48 lists the Status Codes that the SCU of any of the Query/Retrieve FIND SOP Class supports for the C-FIND message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-48. Status Codes C-FIND for Query/Retrieve FIND SOP Classes - SCU

Service Status	Further Meaning	Status Code
Success	Matching is complete - No final identifier is supplied	0000
Failure	Refused: Out of Resources	A700
	Error: Data Set does not match SOP Class	A900
	Error: Unable to process	C000-CFFF
	SOP Class Not Supported	0122
Cancel	Matching terminated due to cancel	FE00
Pending	Matches are continuing - Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys.	FF00
	Matches are continuing - Warning that one or more Optional Keys were not supported for existence for this Identifier	FF01
-	Other Status Codes	anything else

N.7.3.2.7.2 SCU of the Query/Retrieve MOVE SOP Classes - C-MOVE

Table N.7-49 lists the Status Codes that the SCU of any of the Query/Retrieve MOVE SOP Class supports for the C-MOVE message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-49. Status Codes C-MOVE for Query/Retrieve MOVE SOP Classes - SCU

Service Status	Further Meaning	Status Codes	Related Fields
Success	Sub-operations Complete - No Failures	0000	(0000,1020) (0000,1021) (0000,1022) (0000,1023)
Warning	Sub-operations Complete - One or more Failures	B000	(0000,1020) (0000,1022) (0000,1023)
Failed	Out of Resources - Unable to calculate number of matches	A701	(0000,0902)
	Out of Resources - Unable to perform sub-operations	A702	(0000,1020) (0000,1021) (0000,1022) (0000,1023)
	Move Destination unknown	A801	(0000,0902)
	Data Set does not match SOP Class	A900	(0000,0901) (0000,0902)
	Unable to process	Cxxx	(0000,0901) (0000,0902)
Cancel	Sub-operations terminated due to Cancel Indication	FE00	(0000,1020) (0000,1021) (0000,1022) (0000,1023)
Pending	Sub-operations are continuing	FF00	(0000,1020) (0000,1021) (0000,1022) (0000,1023)
-	Other Status Codes	anything else	-

N.7.3.2.7.3 SCP of the Query/Retrieve FIND SOP Classes - C-FIND

Table N.7-50 lists the Status Codes that the SCP of any of the Query/Retrieve FIND SOP Classes supports for the C-FIND message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-50. Status Codes C-FIND for Query/Retrieve FIND SOP Classes - SCP

Service Status	Further Meaning	Status Code
Success	Matching is complete - No final identifier is supplied	0000
Failure	Refused: Out of Resources	A700
	Error: Data Set does not match SOP Class	A900
	Error: Unable to process	C000
	SOP Class Not Supported	0122
Cancel	Matching terminated due to cancel	FE00
Pending	Matches are continuing - Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys.	FF00
	Matches are continuing - Warning that one or more Optional Keys were not supported for existence for this Identifier	FF01

N.7.3.2.7.4 SCP of the Query/Retrieve MOVE SOP Classes - C-MOVE

Table N.7-51 lists the Status Codes that the SCP of any of the Query/Retrieve MOVE SOP Classes supports for the C-MOVE message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

[Describe the action on the C-STORE sub-operation due to above mentioned conditions. Mention what happens to the C-STORE sub-operation when the specific condition occurs.]

Table N.7-51. Status Codes C-MOVE for Query/Retrieve MOVE SOP Classes - SCP

Service Status	Further Meaning	Status Codes	Related Fields sent in the response
Success	Sub-operations Complete - No Failures	0000	(0000,1020) (0000,1021) (0000,1022) (0000,1023)
Warning	Sub-operations Complete - One or more Failures	B000	(0000,1020) (0000,1022) (0000,1023)
Failed	Out of Resources - Unable to calculate number of matches	A701	(0000,0902)
	Out of Resources - Unable to perform sub-operations	A702	(0000,1020) (0000,1021) (0000,1022) (0000,1023)
	Move Destination unknown	A801	(0000,0902)
	Data Set does not match SOP Class	A900	(0000,0901) (0000,0902)
	Unable to process	Cxxx	(0000,0901) (0000,0902)
Cancel	Sub-operations terminated due to Cancel Indication	FE00	(0000,1020) (0000,1021) (0000,1022) (0000,1023)
Pending	Sub-operations are continuing	FF00	(0000,1020) (0000,1021) (0000,1022) (0000,1023)

N.7.3.2.8 Print Management Service

N.7.3.2.8.1 SCU of the Basic Film Session SOP Class

N.7.3.2.8.1.1 SCU of the Basic Film Session SOP Class - N-CREATE

Table N.7-52 lists the Status Codes that the SCU of the Basic Film Session SOP Class supports for the N-CREATE message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-52. Status Codes for N-CREATE of the Basic Film Session SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Attribute List warning	0107
	Attribute Value out of range	0116
	Memory allocation not supported	B600
Failure	No such Attribute	0105
	Invalid Attribute Value	0106
	Processing Failure	0110
	Duplicate SOP Instance	0111
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Missing Attribute	0120
	Missing Attribute Value	0121
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
-	Other Status Codes	anything else

N.7.3.2.8.1.2 SCU of the Basic Film Session SOP Class - N-SET

Table N.7-53 lists the Status Codes that the SCU of the Basic Film Session SOP Class supports for the N-SET message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-53. Status Codes for N-SET of the Basic Film Session SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Attribute List warning	0107
	Attribute Value out of range	0116
	Memory allocation not supported	B600
Failure	No such Attribute	0105
	Invalid Attribute Value	0106
	Processing Failure	0110
	Duplicate SOP Instance	0111
	No such SOP Instance	0112
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class Instance Conflict	0119
	Missing Attribute	0120
	Missing Attribute Value	0121
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
-	Other Status Codes	anything else

N.7.3.2.8.1.3 SCU of the Basic Film Session SOP Class - N-DELETE

Table N.7-54 lists the Status Codes that the SCU of the Basic Film Session SOP Class supports for the N-DELETE message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-54. Status Codes for N-DELETE of the Basic Film Session SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Failure	Processing Failure	0110
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class Instance Conflict	0119
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
-	Other Status Codes	anything else

N.7.3.2.8.1.4 SCU of the Basic Film Session SOP Class - N-ACTION

Table N.7-55 lists the Status Codes that the SCU of the Basic Film Session SOP Class supports for the N-ACTION message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-55. Status Codes for N-Action of the Basic Film Session SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Film belonging to the film session are accepted for printing; if supported, the Print Job SOP Instance is created	0000
Warning	Film session printing (collation) is not supported	B601
	Film Session SOP Instance hierarchy does not contain Image Box SOP Instances (empty page)	B602
	Image size is larger than image box size, the image has been demagnified.	B604
	Image size is larger than the Image Box size. The Image has been cropped to fit.	B609
	Image size or Combined Print Image size is larger than the Image Box size. Image or Combined Print Image has been decimated to fit.	B60A
Failure	Processing failure	0110
	No such SOP Instance	0112
	No Such Argument	0114
	Invalid argument Value	0115
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class-Instance conflict	0119
	No Such Action	0123
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
	Failed: Film Session SOP Instance hierarchy does not contain Film Box SOP Instances	C600
	Failed: Unable to create Print Job SOP Instance; print queue is full	C601
	Failed: Image size is larger than image box size	C603
	Failed: Combined Print Image size is larger than the Image Box size	C613
-	Other Status Codes	anything else

N.7.3.2.8.2 SCU of the Basic Film Box Session SOP Class

N.7.3.2.8.2.1 SCU of the Basic Film Box Session SOP Class - N-CREATE

Table N.7-52 lists the Status Codes that the SCU of the Basic Film Box SOP Class supports for the N-CREATE message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-56. Status Codes for N-CREATE of the Basic Film Box SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Attribute List warning	0107
	Attribute Value out of range	0116
	Requested Min Density or Max Density outside of printer's operating range	B605
Failure	No such Attribute	0105
	Invalid Attribute Value	0106
	Processing Failure	0110
	Duplicate SOP Instance	0111
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Missing Attribute	0120
	Missing Attribute Value	0121
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
	There is an existing Film Box that has not been printed and N-ACTION at the Film Session level is not supported. A new Film Box will not be created when a previous Film Box has not been printed	C616
-	Other Status Codes	anything else

N.7.3.2.8.2.2 SCU of the Basic Film Box Session SOP Class - N-SET

Table N.7-57 lists the Status Codes that the SCU of the Basic Film Box SOP Class supports for the N-SET message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-57. Status Codes for N-SET of the Basic Film Box SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Attribute List warning	0107
	Attribute Value out of range	0116
	Requested Min Density or Max Density outside of printer's operating range	B605
Failure	No such Attribute	0105
	Invalid Attribute Value	0106
	Processing Failure	0110
	Duplicate SOP Instance	0111
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class Instance Conflict	0119
	Missing Attribute	0120
	Missing Attribute Value	0121
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
	There is an existing Film Box that has not been printed and N-ACTION at the Film Session level is not supported. A new Film Box will not be created when a previous Film Box has not been printed	C616
-	Other Status Codes	anything else

N.7.3.2.8.2.3 SCU of the Basic Film Box Session SOP Class - N-DELETE

Table N.7-58 lists the Status Codes that the SCU of the Basic Film Box SOP Class supports for the N-DELETE message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-58. Status Codes for N-DELETE of the Basic Film Box SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Failure	Processing Failure	0110
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class Instance Conflict	0119
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
-	Other Status Codes	anything else

N.7.3.2.8.2.4 SCU of the Basic Film Box Session SOP Class - N-ACTION

Table N.7-59 lists the Status Codes that the SCU of the Basic Film Box SOP Class supports for the N-ACTION message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-59. Status Codes for N-ACTION of the Basic Film Box SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Film Box SOP Instance hierarchy does not contain Image Box SOP Instances (empty page)	B603
	Image size is larger than Image Box size. The image has been demagnified.	B604
	Image size is larger than Image Box size. The image has been cropped to fit.	B609
	Image size or Combined Print Image Size is larger than Image Box size. The image or combined Print Image has been decimated to fit.	B60A
Failure	Processing failure	0110
	No such SOP Instance	0112
	No Such Argument	0114
	Invalid argument Value	0115
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class-Instance conflict	0119
	No Such Action	0123
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
	Unable to create Print Job SOP Instance; print queue is full.	C602
	Image size is larger than Image Box size.	C603
	Combined Print Image Size is larger than Image Box size.	C613
-	Other Status Codes	anything else

N.7.3.2.8.3 SCU of the Basic Grayscale Image Box SOP Class - N-SET

Table N.7-60 lists the Status Codes that the SCU of the Basic Grayscale Image Box SOP Class supports for the N-SET message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-60. Status Codes for N-SET of the Grayscale Image Box SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Image size is larger than Image Box size. The image has been demagnified.	B604
	Requested Min Density or Max Density outside of printer's operating range.	B605
	Image size is larger than Image Box size. The image has been cropped to fit.	B609
	Image size or Combined Print Image Size is larger than Image Box size. The image or combined Print Image has been decimated to fit.	B60A
Failure	No such Attribute	0105
	Invalid Attribute Value	0106
	Processing Failure	0110
	Duplicate SOP Instance	0111
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class Instance Conflict	0119
	Missing Attribute	0120
	Missing Attribute Value	0121
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
	Image size is larger than Image Box size.	C603
	Insufficient memory in printer to store the image.	C605
	Combined Print Image Size is larger than Image Box size.	C613
-	Other Status Codes	anything else

N.7.3.2.8.4 SCU of the Basic Color Image Box SOP Class - N-SET

Table N.7-61 lists the Status Codes that the SCU of the Basic Color Image Box SOP Class supports for the N-SET message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-61. Status Codes for N-SET of the Color Image Box SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Image size is larger than Image Box size. The image has been demagnified.	B604
	Image size is larger than Image Box size. The image has been cropped to fit.	B609
	Image size or Combined Print Image Size is larger than Image Box size. The image or combined Print Image has been decimated to fit.	B60A
Failure	No such Attribute	0105
	Invalid Attribute Value	0106
	Processing Failure	0110
	Duplicate SOP Instance	0111
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class Instance Conflict	0119
	Missing Attribute	0120
	Missing Attribute Value	0121
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
	Image size is larger than Image Box size.	C603
	Insufficient memory in printer to store the image.	C605
	Combined Print Image Size is larger than Image Box size.	C613
-	Other Status Codes	anything else

N.7.3.2.8.5 SCU of the Printer SOP Class

N.7.3.2.8.5.1 SCU of the Printer SOP Class - N-EVENT-REPORT

Table N.7-62 lists the Status Codes that the SCU of Printer SOP Class supports for the N-EVENT-REPORT message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-62. Status Codes for N-EVENT-REPORT of the Printer SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Failure	Processing Failure	0110
	No such SOP Instance	0112
	No Such Event Type	0113
	No Such Argument	0114
	Invalid Argument Value	0115
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class-Instance conflict	0119
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
-	Other Status Codes	anything else

N.7.3.2.8.5.2 SCU of the Printer SOP Class - N-GET

Table N.7-63 lists the Status Codes that the SCU of the Printer SOP Class supports for the N-GET message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-63. Status Codes for N-GET of the Printer SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Attribute List warning	0107
Failure	Processing Failure	0110
	No such SOP Instance	0112
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class-Instance conflict	0119
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
-	Other Status Codes	anything else

N.7.3.2.8.6 SCU of the Basic Annotation Box SOP Class - N-SET

Table N.7-64 lists the Status Codes that the SCU of the Basic Annotation Box SOP Class supports for the N-SET message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-64. Status Codes for N-SET of the Basic Annotation Box SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Failure	No such Attribute	0105
	Invalid Attribute Value	0106
	Processing Failure	0110
	Duplicate SOP Instance	0111
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class Instance Conflict	0119
	Missing Attribute	0120
	Missing Attribute Value	0121
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
-	Other Status Codes	anything else

N.7.3.2.8.7 SCU of the Print Job SOP Class

N.7.3.2.8.7.1 SCU of the Print Job SOP Class - N-EVENT-REPORT

Table N.7-65 lists the Status Codes that the SCU of the Print Job SOP Class supports for the N-EVENT-REPORT message and defines the application behavior when encountering the listed Status Codes.

[Describe the behavior of the application when it receives any of the Status Codes listed in the table below, e.g., displaying and logging the error code or retrying the request. If any other Status Code is supported add it to the table.] In the "other Status Codes" row document the behavior of the application in case it encounters and unknown Status Code.]

Table N.7-65. Status Codes N-EVENT-REPORT of the Print Job SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Failure	Processing Failure	0110
	No such SOP Instance	0112
	No Such Event Type	0113
	No Such Argument	0114
	Invalid Argument Value	0115
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class-Instance conflict	0119
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
-	Other Status Codes	anything else

N.7.3.2.8.7.2 SCU of the Print Job SOP Class - N-GET

Table N.7-66 lists the Status Codes that the SCU of Print Job SOP Class supports for the N-GET message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-66. Status Codes for N-GET of the Print Job SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Attribute List warning	0107
Failure	Processing Failure	0110
	No such SOP Instance	0112
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class-Instance conflict	0119
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
-	Other Status Codes	anything else

N.7.3.2.8.8 SCU of the Presentation LUT SOP Class

N.7.3.2.8.8.1 SCU of the Presentation LUT SOP Class - N-CREATE

Table N.7-67 lists the Status Codes that the SCU of the Presentation LUT SOP Class supports for the N-CREATE message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-67. Status Codes N-CREATE of the Presentation LUT SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Attribute List warning	0107
	Attribute Value out of range	0116
	Requested Min Density or Max Density outside of printer's operating range	B605
Failure	No such Attribute	0105
	Invalid Attribute Value	0106
	Processing Failure	0110
	Duplicate SOP Instance	0111
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Missing Attribute	0120
	Missing Attribute Value	0121
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
-	Other Status Codes	anything else

N.7.3.2.8.8.2 SCU of the Presentation LUT SOP Class - N-DELETE

Table N.7-68 lists the Status Codes that the SCU of the Presentation LUT SOP Class supports for the N-DELETE message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-68. Status Codes for N-DELETE of the Presentation LUT SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Failure	Processing Failure	0110
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class Instance Conflict	0119
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
-	Other Status Codes	anything else

N.7.3.2.8.9 SCU of the Printer Configuration Retrieval SOP Class - N-GET

Table N.7-69 lists the Status Codes that the SCU of the Printer Configuration SOP Class supports for the N-GET message and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-69. Status Codes N-GET of the Printer Configuration Retrieval SOP Class - SCU

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Attribute List warning	0107
Failure	Processing Failure	0110
	No such SOP Instance	0112
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class-Instance conflict	0119
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
-	Other Status Codes	anything else

N.7.3.2.8.10 SCP of the Basic Film Session SOP Class

N.7.3.2.8.10.1 SCP of the Basic Film Session SOP Class - N-CREATE

Table N.7-70 lists the Status Codes that the SCP of the Basic Film Session SOP Class supports for the N-CREATE message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-70. Status Codes for N-CREATE of the Basic Film Session SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Memory allocation not supported	B600
	Attribute Value out of range	0116
	Attribute List warning	0107
Failure	No such Attribute	0105
	Invalid Attribute Value	0106
	Processing Failure	0110
	Duplicate SOP Instance	0111
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Missing Attribute	0120
	Missing Attribute Value	0121
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213

N.7.3.2.8.10.2 SCP of the Basic Film Session SOP Class - N-SET

Table N.7-71 lists the Status Codes that the SCP of the Basic Film Session SOP Class supports for the N-SET message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-71. Status Codes for N-SET of the Basic Film Session SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Attribute Value out of range	0116
Warning	Attribute List warning	0107
Failure	No such Attribute	0105
	Invalid Attribute Value	0106
	Processing Failure	0110
	Duplicate SOP Instance	0111
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Missing Attribute	0120
	Missing Attribute Value	0121
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213

N.7.3.2.8.10.3 SCP of the Basic Film Session SOP Class - N-DELETE

Table N.7-72 lists the Status Codes that the SCP of the Basic Film Session SOP Class supports for the N-DELETE message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-72. Status Codes for N-DELETE of the Basic Film Session SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Failure	Processing Failure	0110
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class Instance Conflict	0119
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213

N.7.3.2.8.10.4 SCP of the Basic Film Session SOP Class - N-ACTION

Table N.7-73 lists the Status Codes that the SCP of the Basic Film Session SOP Class supports for the N-ACTION message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-73. Status Codes for N-ACTION of the Basic Film Session SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Film belonging to the film session are accepted for printing; if supported, the Print Job SOP Instance is created	0000
Warning	Film session printing (collation) is not supported	B601
	Film Session SOP Instance hierarchy does not contain Image Box SOP Instances (empty page)	B602
	Image size is larger than image box size, the image has been demagnified.	B604
	Image size is larger than the Image Box size. The Image has been cropped to fit.	B609
	Image size or Combined Print Image size is larger than the Image Box size. Image or Combined Print Image has been decimated to fit.	B60A
Failure	Failed: Film Session SOP Instance hierarchy does not contain Film Box SOP Instances	C600
	Failed: Unable to create Print Job SOP Instance; print queue is full	C601
	Failed: Image size is larger than image box size	C603
	Failed: Combined Print Image size is larger than the Image Box size	C613

N.7.3.2.8.11 SCP of the Basic Film Box SOP Class

N.7.3.2.8.11.1 SCP of the Basic Film Box SOP Class - N-CREATE

Table N.7-74 lists the Status Codes that the SCP of the Basic Film Box SOP Class supports for the N-CREATE message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-74. Status Codes for N-CREATE of the Basic Film Box SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Attribute List warning	0107
	Attribute Value out of range	0116
	Requested Min Density or Max Density outside of printer's operating range	B605
Failure	No such Attribute	0105
	Invalid Attribute Value	0106
	Processing Failure	0110
	Duplicate SOP Instance	0111
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Missing Attribute	0120
	Missing Attribute Value	0121
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
	There is an existing Film Box that has not been printed and N-ACTION at the Film Session level is not supported. A new Film Box will not be created when a previous Film Box has not been printed	C616

N.7.3.2.8.11.2 SCP of the Basic Film Box SOP Class - N-SET

Table N.7-75 lists the Status Codes that the SCP of the Basic Film Box SOP Class supports for the N-SET message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-75. Status Codes for N-SET of the Basic Film Box SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Attribute List warning	0107
	Attribute Value out of range	0116
	Requested Min Density or Max Density outside of printer's operating range	B605
Failure	No such Attribute	0105
	Invalid Attribute Value	0106
	Processing Failure	0110
	Duplicate SOP Instance	0111
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class Instance Conflict	0119
	Missing Attribute	0120
	Missing Attribute Value	0121
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
	There is an existing Film Box that has not been printed and N-ACTION at the Film Session level is not supported. A new Film Box will not be created when a previous Film Box has not been printed	C616

N.7.3.2.8.11.3 SCP of the Basic Film Box SOP Class - N-DELETE

Table N.7-76 lists the Status Codes that the SCP of the Basic Film Box SOP Class supports for the N-DELETE message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-76. Status Codes for N-DELETE of the Basic Film Box SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Failure	Processing Failure	0110
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class Instance Conflict	0119
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213

N.7.3.2.8.11.4 SCP of the Basic Film Box SOP Class - N-ACTION

Table N.7-77 lists the Status Codes that the SCP of the Basic Film Box SOP Class supports for the N-ACTION message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-77. Status Codes for N-ACTION of the Basic Film Box SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Film Box SOP Instance hierarchy does not contain Image Box SOP Instances (empty page)	B603
	Image size is larger than Image Box size. The image has been demagnified.	B604
	Image size is larger than Image Box size. The image has been cropped to fit.	B609
	Image size or Combined Print Image Size is larger than Image Box size. The image or combined Print Image has been decimated to fit.	B60A
Failure	Processing failure	0110
	No such SOP Instance	0112
	No Such Argument	0114
	Invalid argument Value	0115
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class-Instance conflict	0119
	No Such Action	0123
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
	Unable to create Print Job SOP Instance; print queue is full.	C602
	Image size is larger than Image Box size.	C603
	Combined Print Image Size is larger than Image Box size.	C613

N.7.3.2.8.12 SCP of the Basic Grayscale Image Box SOP Class - N-SET

Table N.7-78 lists the Status Codes that the SCP of the Basic Grayscale Image Box SOP Class supports for the N-SET message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-78. Status Codes for N-SET of the Basic Grayscale Image Box SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Image size is larger than Image Box size. The image has been demagnified.	B604
	Requested Min Density or Max Density outside of printer's operating range.	B605
	Image size is larger than Image Box size. The image has been cropped to fit.	B609
	Image size or Combined Print Image Size is larger than Image Box size. The image or combined Print Image has been decimated to fit.	B60A
Failure	No such Attribute	0105
	Invalid Attribute Value	0106
	Processing Failure	0110
	Duplicate SOP Instance	0111
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class Instance Conflict	0119
	Missing Attribute	0120
	Missing Attribute Value	0121
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
	Image size is larger than Image Box size.	C603
	Insufficient memory in printer to store the image.	C605
	Combined Print Image Size is larger than Image Box size.	C613

N.7.3.2.8.13 SCP of the Basic Color Image Box SOP Class - N-SET

Table N.7-79 lists the Status Codes that the SCP of the Basic Color Image Box SOP Class supports for the N-SET message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-79. Status Codes for N-SET of the Basic Color Image Box SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Image size is larger than Image Box size. The image has been demagnified.	B604
	Requested Min Density or Max Density outside of printer's operating range.	B605
	Image size is larger than Image Box size. The image has been cropped to fit.	B609
	Image size or Combined Print Image Size is larger than Image Box size. The image or combined Print Image has been decimated to fit.	B60A
Failure	No such Attribute	0105
	Invalid Attribute Value	0106
	Processing Failure	0110
	Duplicate SOP Instance	0111
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class Instance Conflict	0119
	Missing Attribute	0120
	Missing Attribute Value	0121
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213
	Image size is larger than Image Box size.	C603
	Insufficient memory in printer to store the image.	C605
	Combined Print Image Size is larger than Image Box size.	C613

N.7.3.2.8.14 SCP of the Printer SOP Class

N.7.3.2.8.14.1 SCP of the Printer SOP Class - N-EVENT-REPORT

Table N.7-80 lists the Status Codes that the SCP of the Printer SOP Class supports for the N-EVENT-REPORT message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-80. Status Codes for N-EVENT-REPORT of the Printer SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Failure	Processing Failure	0110
	No such SOP Instance	0112
	No Such Event Type	0113
	No Such Argument	0114
	Invalid Argument Value	0115
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class-Instance conflict	0119
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213

N.7.3.2.8.14.2 SCP of the Printer SOP Class - N-GET

Table N.7-81 lists the Status Codes that the SCP of the Printer SOP Class supports for the N-GET message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-81. Status Codes for N-GET of the Printer SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Attribute List warning	0107
Failure	Processing Failure	0110
	No such SOP Instance	0112
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class-Instance conflict	0119
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213

N.7.3.2.8.15 SCP the Basic Annotation Box SOP Class - N-SET

Table N.7-82 lists the Status Codes that the SCP of the Basic Annotation Box SOP Class supports for the N-SET message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-82. Status Codes for N-SET of the Basic Annotation Box SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Failure	No such Attribute	0105
	Invalid Attribute Value	0106
	Processing Failure	0110
	Duplicate SOP Instance	0111
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class Instance Conflict	0119
	Missing Attribute	0120
	Missing Attribute Value	0121
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213

N.7.3.2.8.16 SCP of the Print Job SOP Class

N.7.3.2.8.16.1 SCP of the Print Job SOP Class - N-EVENT-REPORT

Table N.7-83 lists the Status Codes that the SCP of the Print Job SOP Class supports for the N-EVENT-REPORT message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-83. Status Codes for N-EVENT-REPORT of the Print Job SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Failure	Processing Failure	0110
	No such SOP Instance	0112
	No Such Event Type	0113
	No Such Argument	0114
	Invalid Argument Value	0115
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class-Instance conflict	0119
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213

N.7.3.2.8.16.2 SCP of the Print Job SOP Class - N-GET

Table N.7-84 lists the Status Codes that the SCP of the Print Job SOP Class supports for the N-GET message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-84. Status Codes for N-GET of the Print Job SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Attribute List warning	0107
Failure	Processing Failure	0110
	No such SOP Instance	0112
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class-Instance conflict	0119
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213

N.7.3.2.8.17 SCP of the Presentation LUT SOP Class

N.7.3.2.8.17.1 SCP of the Presentation LUT SOP Class - N-CREATE

Table N.7-85 lists the Status Codes that the SCP of the Presentation LUT SOP Class supports for the N-CREATE message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-85. Status Codes for N-CREATE of the Presentation LUT SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Attribute List warning	0107
	Attribute Value out of range	0116
	Requested Min Density or Max Density outside of printer's operating range	B605
Failure	No such Attribute	0105
	Invalid Attribute Value	0106
	Processing Failure	0110
	Duplicate SOP Instance	0111
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Missing Attribute	0120
	Missing Attribute Value	0121
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213

N.7.3.2.8.17.2 SCP of the Presentation LUT SOP Class - N-DELETE

Table N.7-86 lists the Status Codes that the SCP of the Presentation LUT SOP Class supports for the N-DELETE message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-86. Status Codes for N-DELETE of the Presentation LUT SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Failure	Processing Failure	0110
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class Instance Conflict	0119
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213

N.7.3.2.8.18 SCP of the Printer Configuration Retrieval SOP Class - N-GET

Table N.7-87 lists the Status Codes that the SCP of the Printer Configuration SOP Class supports for the N-GET message and defines conditions in which the listed Status Codes are sent.

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-87. Status Codes for N-GET of the Printer Configuration Retrieval SOP Class - SCP

Service Status	Further Meaning	Status Code
Success	Success	0000
Warning	Attribute List warning	0107
Failure	Processing Failure	0110
	No such SOP Instance	0112
	Invalid SOP Instance	0117
	No such SOP Class	0118
	Class-Instance conflict	0119
	Refused: Not authorized	0124
	Duplicate invocation	0210
	Unrecognized operation	0211
	Mistyped argument	0212
	Resource limitation	0213

N.7.3.3 DICOM Web Services

N.7.3.3.1 General Status Codes

This section describes the common Status Code behavior and handling all the supported transaction.

N.7.3.3.1.1 Common Transaction as Origin Server

Table N.7-88 lists the Status Codes that an origin server supports for all transactions and the conditions in which the listed Status Codes are sent:

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-88. Status Codes of Origin Server for all Transactions

Status	Code	Condition
Success	200 (Success)
	201 (Created)
	202 (Accepted)
	203 (Non-Authoritative Information)
	204 (No-Content)
	205 (Reset Content)
	206 (Partial Content)
Redirection	301 (Moved Permanently)
	303 (See Other)
	304 (Not Modified)
Client Error	400 (Bad Request)
	401 (Unauthorized)
	403 (Forbidden)
	404 (Not Found)
	405 (Method Not Allowed)
	406 (Not Acceptable)
	409 (Conflict)
	410 (Gone)
	411 (Length Required)
	413 (Payload Too Large)
	414 (URI Too Long)
	415 (Unsupported Media Type)
Server Error	500 (Internal Server Error)
	501 (Not Implemented)
	503 (Service Unavailable)
	505 (HTTP Version Not Supported)

N.7.3.3.1.2 Common Transaction as User Agent

Table N.7-89 lists the Status Codes that a user agent supports for all transactions and defines the application behavior when encountering the listed Status Codes:

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-89. Status Codes of User Agent for all Transactions

Status	Code	Behavior
Success	200 (Success)
	201 (Created)
	202 (Accepted)
	203 (Non-Authoritative Information)
	204 (No-Content)
	205 (Reset Content)
	206 (Partial Content)
Redirection	301 (Moved Permanently)
	303 (See Other)
	304 (Not Modified)
Client Error	400 (Bad Request)
	401 (Unauthorized)
	403 (Forbidden)
	404 (Not Found)
	405 (Method Not Allowed)
	406 (Not Acceptable)
	409 (Conflict)
	410 (Gone)
	411 (Length Required)
	413 (Payload Too Large)
	414 (URI Too Long)
	415 (Unsupported Media Type)
Server Error	500 (Internal Server Error)
	501(Not Implemented)
	503 (Service Unavailable)
	505 (HTTP Version Not Supported)
-	Other Status Codes

N.7.3.3.2 URI Web Service

N.7.3.3.2.1 URI Web Service as Origin Server

Table N.7-90 lists the Status Codes that an origin server supports for the URI Web Service and the conditions in which the listed Status Codes are sent:

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-90. Status Codes of Origin Server for URI Service

Status	Code	Condition
Success	200 (OK)
Failure	400 (Bad)
	404 (Not Found)
	410 (Gone)

N.7.3.3.2.2 URI Web Service as User Agent

Table N.7-91 lists the Status Codes that a user agent supports for the URI Web Service and defines the application behavior when encountering the listed Status Codes.

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-91. Status Codes of User Agent for URI Service

Status	Code	Behavior
Success	200 (OK)
Failure	400 (Bad)
	404 (Not Found)
	410 (Gone)
-	Other Status Codes

N.7.3.3.3 Studies Web Service

N.7.3.3.3.1 Retrieve Transaction as Origin Server

Table N.7-92 lists the Status Codes that an origin server supports for the Retrieve Transaction of the Studies Web Service and the conditions in which the listed Status Codes are sent:

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-92. Status Codes of Origin Server for Retrieve Transaction

Status	Code	Condition
Success	200 (OK)
Success	206 (Partial Content)
Failure	400 (Bad Request)
	404 (Not Found)
	406 (Not Acceptable)
	410 (Gone)
	413 (Payload Too Large)

N.7.3.3.3.2 Retrieve Transaction as User Agent

Table N.7-93 lists the Status Codes that a user agent supports for the Retrieve Transaction of the Studies Web Service and defines the application behavior when encountering the listed Status Codes:

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-93. Status Codes of User Agent for Retrieve Transaction

Status	Code	Behavior
Success	200 (OK)
Success	206 (Partial Content)
Failure	400 (Bad Request)
	404 (Not Found)
	406 (Not Acceptable)
	410 (Gone)
	413 (Payload Too Large)
-	Other Status Codes

N.7.3.3.3.3 Store Transaction as Origin Server

Table N.7-94 lists the Status Codes that an origin server supports for the Store Transaction of the Studies Web Service and the conditions in which the listed Status Codes are sent:

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-94. Status Codes of Origin Server for Store Transaction

Status	Code	Condition
Success	200 (OK)
Success	202 (Accepted)
Failure	400 (Bad Request)
	409 (Conflict)
	415 (Unsupported Media Type)

N.7.3.3.3.4 Store Transaction as User Agent

Table N.7-95 lists the Status Codes that a user agent supports for the Store Transaction of the Studies Web Service and defines the application behavior when encountering the listed Status Codes:

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-95. Status Codes of User Agent for Store Transaction

Status	Code	Behavior
Success	200 (OK)
Success	202 (Accepted)
Failure	400 (Bad Request)
	409 (Conflict)
	415 (Unsupported Media Type)
-	Other Status Codes

N.7.3.3.3.5 Search Transaction as Origin Server

Table N.7-96 lists the Status Codes that an origin server supports for the Search Transaction of the Studies Web Service and the conditions in which the listed Status Codes are sent:

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-96. Status Codes of Origin Server for Search Transaction

Status	Code	Condition
Success	200 (OK)
Success	204 (No Content)
Failure	400 (Bad Request)
Failure	413 (Payload Too Large)

N.7.3.3.3.6 Search Transaction as User Agent

Table N.7-97 lists the Status Codes that a user agent supports for the Search Transaction of the Studies Web Service and defines the application behavior when encountering the listed Status Codes:

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-97. Status Codes of User Agent for Search Transaction

Status	Code	Behavior
Success	200 (OK)
Success	204 (No Content)
Failure	400 (Bad Request)
Failure	413 (Payload Too Large)
-	Other Status Codes

N.7.3.3.4 Worklist Web Service

N.7.3.3.4.1 Create Transaction as Origin Server

Table N.7-98 lists the Status Codes that an origin server supports for the Create Transaction of the Worklist Web Service and the conditions in which the listed Status Codes are sent:

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-98. Status Codes of Origin Server for Create Transaction

Status	Code	Condition
Success	201 (Created)
Failure	400 (Bad Request)
Failure	409 (Conflict)

N.7.3.3.4.2 Create Transaction as User Agent

Table N.7-99 lists the Status Codes that a user agent supports for the Create Transaction of the Worklist Web Service and defines the application behavior when encountering the listed Status Codes:

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-99. Status Codes of User Agent for Create Transaction

Status	Code	Behavior
Success	201 (Created)
Failure	400 (Bad Request)
Failure	409 (Conflict)
-	Other Status Codes

N.7.3.3.4.3 Retrieve Workitem Transaction as Origin Server

Table N.7-100 lists the Status Codes that an origin server supports for the Retrieve Workitem Transaction of the Worklist Web Service and the conditions in which the listed Status Codes are sent:

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-100. Status Codes of Origin Server for Retrieve Workitem Transaction

Status	Code	Condition
Success	200 (OK)
Failure	400 (Bad Request)
	404 (Not Found)
	409 (Conflict)
	410 (Gone)

N.7.3.3.4.4 Retrieve Workitem Transaction as User Agent

Table N.7-101 lists the Status Codes that a user agent supports for the Retrieve Workitem Transaction of the Worklist Web Service and defines the application behavior when encountering the listed Status Codes:

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-101. Status Codes of User Agent for Retrieve Workitem Transaction

Status	Code	Behavior
Success	200 (OK)
Failure	400 (Bad Request)
	404 (Not Found)
	409 (Conflict)
	410 (Gone)
-	Other Status Codes

N.7.3.3.4.5 Update Workitem Transaction as Origin Server

Table N.7-102 lists the Status Codes that an origin server supports for the Update Workitem Transaction of the Worklist Web Service and the conditions in which the listed Status Codes are sent:

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-102. Status Codes of Origin Server for Update Workitem Transaction

Status	Code	Condition
Success	200 (OK)
Failure	400 (Bad Request)
	404 (Not Found)
	409 (Conflict)
	410 (Gone)

N.7.3.3.4.6 Update Workitem Transaction as User Agent

Table N.7-103 lists the Status Codes that a user agent supports for the Update Workitem Transaction of the Worklist Web Service and defines the application behavior when encountering the listed Status Codes:

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-103. Status Codes of User Agent for Update Workitem Transaction

Status	Code	Behavior
Success	200 (OK)
Failure	400 (Bad Request)
	404 (Not Found)
	409 (Conflict)
	410 (Gone)
-	Other Status Codes

N.7.3.3.4.7 Change Workitem State Transaction as Origin Server

Table N.7-104 lists the Status Codes that an origin server supports for the Change Workitem State Transaction of the Worklist Web Service and the conditions in which the listed Status Codes are sent:

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-104. Status Codes of Origin Server for Change Workitem State Transaction

Status	Code	Condition
Success	200 (OK)
Failure	400 (Bad Request)
	404 (Not Found)
	409 (Conflict)
	410 (Gone)

N.7.3.3.4.8 Change Workitem State Transaction as User Agent

Table N.7-105 lists the Status Codes that a user agent supports for the Change Workitem Transaction of the Worklist Web Service and defines the application behavior when encountering the listed Status Codes:

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-105. Status Codes of User Agent for Change Workitem State Transaction

Status	Code	Behavior
Success	200 (OK)
Failure	400 (Bad Request)
	404 (Not Found)
	409 (Conflict)
	410 (Gone)
-	Other Status Codes

N.7.3.3.4.9 Request Cancellation Transaction as Origin Server

Table N.7-106 lists the Status Codes that an origin server supports for the Request Cancellation of the Worklist Web Service and the conditions in which the listed Status Codes are sent:

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-106. Status Codes of Origin Server for Request Cancellation Transaction

Status	Code	Condition
Success	202 (Accepted)
Failure	400 (Bad Request)
	404 (Not Found)
	409 (Conflict)

N.7.3.3.4.10 Request Cancellation Transaction as User Agent

Table N.7-107 lists the Status Codes that a user agent supports for the Request Cancellation Transaction of the Worklist Web Service and defines the application behavior when encountering the listed Status Codes:

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-107. Status Codes of User Agent for Request Cancellation Transaction

Status	Code	Behavior
Success	202 (Accepted)
Failure	400 (Bad Request)
	404 (Not Found)
	409 (Conflict)
-	Other Status Codes

N.7.3.3.4.11 Search Transaction as Origin Server

Table N.7-108 lists the Status Codes that an origin server supports for the Search Transaction of the Worklist Web Service and the conditions in which the listed Status Codes are sent:

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-108. Status Codes of Origin Server for Search Transaction

Status	Code	Condition
Success	200 (OK)
	204 (No Content)
	206 (Partial Content)
Failure	400 (Bad Request)
Failure	413 (Payload Too Large)

N.7.3.3.4.12 Search Transaction as User Agent

Table N.7-109 lists the Status Codes that a user agent supports for the Search Transaction of the Worklist Web Service and defines the application behavior when encountering the listed Status Codes:

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-109. Status Codes of User Agent for Search Transaction

Status	Code	Behavior
Success	200 (OK)
	204 (No Content)
	206 (Partial Content)
Failure	400 (Bad Request)
Failure	413 (Payload Too Large)
-	Other Status Codes

N.7.3.3.4.13 Subscribe Transaction as Origin Server

Table N.7-110 lists the Status Codes that an origin server supports for the Subscribe Transaction of the Worklist Web Service and the conditions in which the listed Status Codes is sent:

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-110. Status Codes of Origin Server for Subscribe Transaction

Status	Code	Condition
Success	201 (Created)
Failure	400 (Bad Request)
	403 (Forbidden)
	404 (Not Found)

N.7.3.3.4.14 Subscribe Transaction as User Agent

Table N.7-111 lists the Status Codes that a user agent supports for the Subscribe Transaction of the Worklist Web Service and defines the application behavior when encountering the listed Status Codes:

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-111. Status Codes of User Agent for Subscribe Transaction

Status	Code	Behavior
Success	201 (Created)
Failure	400 (Bad Request)
	403 (Forbidden)
	404 (Not Found)
-	Other Status Codes

N.7.3.3.4.15 Unsubscribe Transaction as Origin Server

Table N.7-112 lists the Status Codes that an origin server supports for the Unsubscribe Transaction of the Worklist Web Service and the conditions in which the listed Status Codes are sent:

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-112. Status Codes of Origin Server for Unsubscribe Transaction

Status	Code	Condition
Success	200 (OK)
Failure	400 (Bad Request)
	404 (Not Found)

N.7.3.3.4.16 Unsubscribe Transaction as User Agent

Table N.7-113 lists the Status Codes that a user agent supports for the Unsubscribe Transaction of the Worklist Web Service and defines the application behavior when encountering the listed Status Codes:

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-113. Status Codes of User Agent for Unsubscribe Transaction

Status	Code	Behavior
Success	200 (OK)
Failure	400 (Bad Request)
Failure	404 (Not Found)
-	Other Status Codes

N.7.3.3.4.17 Suspend Global Subscription Transaction as Origin Server

Table N.7-114 lists the Status Codes that an origin server supports for the Suspend Global Subscription Transaction of the Worklist Web Service and the conditions in which the listed Status Codes are sent:

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-114. Status Codes of Origin Server for Suspend Global Subscription Transaction

Status	Code	Condition
Success	200 (OK)
Failure	400 (Bad Request)
Failure	404 (Not Found)

N.7.3.3.4.18 Suspend Global Subscription Transaction as User Agent

Table N.7-115 lists the Status Codes that a user agent supports for the Suspend Global Subscription Transaction of the Worklist Web Service and defines the application behavior when encountering the listed Status Codes:

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-115. Status Codes of User Agent for Suspend Global Subscription Transaction

Status	Code	Behavior
Success	200 (OK)
Failure	400 (Bad Request)
Failure	404 (Not Found)
-	Other Status Codes

N.7.3.3.5 Non-Patient Instance Web Service

N.7.3.3.5.1 Retrieve Transaction as Origin Server

Table N.7-116 lists the Status Codes that an origin server supports for the Retrieve Transaction of the Non-Patient Instance Web Service and the conditions in which the listed Status Codes are sent:

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-116. Status Codes of Origin Server for Retrieve Transaction

Status	Code	Condition
Success	200 (OK)
Failure	400 (Bad Request)
	404 (Not Found)
	406 (Unsupported Media Type)

N.7.3.3.5.2 Retrieve Transaction as User Agent

Table N.7-117 lists the Status Codes that a user agent supports for the Retrieve Transaction of the Non-Patient Instance Web Service and defines the application behavior when encountering the listed Status Codes:

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-117. Status Codes of User Agent for Retrieve Transaction

Status	Code	Behavior
Success	200 (OK)
Failure	400 (Bad Request)
	404 (Not Found)
	406 (Unsupported Media Type)
-	Other Status Codes

N.7.3.3.5.3 Store Transaction as Origin Server

Table N.7-118 lists the Status Codes that an origin server supports for the Store Transaction of the Non-Patient Instance Web Service and the conditions in which the listed Status Codes are sent:

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-118. Status Codes of Origin Server for Search Transaction

Status	Code	Condition
Success	200 (OK)
Success	202 (Accepted)
Failure	400 (Bad Request)
	404 (Not Found)
	409 (Conflict)
	415 (Unsupported Media Type)

N.7.3.3.5.4 Store Transaction as User Agent

Table N.7-119 lists the Status Codes that a user agent supports for the Store Transaction of the Non-Patient Instance Web Service and defines the application behavior when encountering the listed Status Codes:

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-119. Status Codes of User Agent for Store Transaction

Status	Code	Behavior
Success	200 (OK)
Success	202 (Accepted)
Failure	400 (Bad Request)
	404 (Not Found)
	409 (Conflict)
	415 (Unsupported Media Type)
-	Other Status Codes

N.7.3.3.5.5 Search Transaction as Origin Server

Table N.7-120 lists the Status Codes that an origin server supports for the Search Transaction of the Non-Patient Instance Web Service and the conditions in which the listed Status Codes are sent:

[Describe the condition which causes the application to send the specific Status Codes. For each other Status Code used add a row to the table.]

Table N.7-120. Status Codes of Origin Server for Search Transaction

Status	Code	Condition
Success	200 (OK)
Failure	406 (Unsupported Media Type)
Failure	413 (Payload Too Large)

N.7.3.3.5.6 Search Transaction as User Agent

Table N.7-121 lists the Status Codes that a user agent supports for the Search Transaction of the Non-Patient Instance Web Service and defines the application behavior when encountering the listed Status Codes:

In the "Other Status Codes" row document the behavior of the application in case it encounters an unknown Status Code.]

Table N.7-121. Status Codes of User Agent for Search Transaction

Status	Code	Behavior
Success	200 (OK)
Failure	406 (Unsupported Media Type)
Failure	413 (Payload Too Large)
-	Other Status Codes

N.7.3.3.6 Storage Commitment Service

N.7.3.3.6.1 Request Transaction As Origin Server

Table N.7.3.3.6.1-1 lists the Status Codes that an origin server supports for the Request Transaction of the Storage Commitment Service and the condition in which any of the listed Status Codes is sent.

[Describe below the condition in which the application sends the specific Status Codes in the Request Transaction response as origin server.]

Table N.7.3.3.6.1-1. Status Codes of Origin Server for Request Transaction

Status	Code	Condition
Success	200 (OK)	The origin server finished processing the storage commitment request
Success	202 (Accepted)	The origin server has not finished processing the storage commitment request yet
Failure	400 (Bad Request)	The origin server cannot handle the storage commitment request because of errors in the request headers or parameters
	409 (Conflict)	The origin server cannot handle the storage commitment request because the provided transaction UID is already in use
	503 (Service Unavailable)	The origin server cannot handle the storage commitment request; this may be a temporal or permanent state

N.7.3.3.6.2 Request Transaction As User Agent

Table N.7.3.3.6.2-1 lists the Status Codes that a user agent supports for the Request Transaction of the Storage Commitment Service and defines the application behavior, when encountering any of the listed Status Codes.

[Describe below the behavior of the application when it receives various Status Codes in the Request Transaction response.]

Table N.7.3.3.6.2-1. Status Codes of User Agent for Request Transaction

Status	Code	Behavior
Success	200 (OK)	Mark all SOP Instances for which the origin server committed safe storage as ready for deletion
Success	202 (Accepted)	Retry later to get the result of the request
Failure	400 (Bad Request)	Reformat the request to proper HTTP
Failure	409 (Conflict)	Retry with another transaction UID
*	Any other code	Do further analysis

N.7.3.3.6.3 Result Check Transaction As Origin Server

Table N.7.3.3.6.3-1 lists the Status Codes that an origin server supports for the Result Check Transaction of the Storage Commitment Service and the condition in which any of the listed Status Codes is sent.

[Describe below the condition in which the application sends the specific Status Codes in the Result Check Transaction response as origin server.]

Table N.7.3.3.6.3-1. Status Codes of Origin Server for Result Check Transaction

Status	Code	Condition
Success	200 (OK)	The origin server finished processing the storage commitment request
Success	202 (Accepted)	The origin server has not finished processing the storage commitment request yet
Failure	404 (Not Found)	The origin server cannot find the storage commitment request result
	410 (Gone)	The origin server can no longer provide the storage commitment request result
	503 (Service Unavailable)	The origin server cannot handle the result check request; this may be a temporary or permanent state

N.7.3.3.6.4 Result Check Transaction As User Agent

Table N.7.3.3.6.4-1 lists the Status Codes that a user agent supports for the Result Check Transaction of the Storage Commitment Service and defines the application behavior when encountering any of the listed Status Codes.

[Describe below the behavior of the application when it receives various Status Codes in the Result Check Transaction response.]

Table N.7.3.3.6.4-1. Status Codes of User Agent for Result Check Transaction

Status	Code	Behavior
Success	200 (OK)	Mark all SOP Instances for which the origin server committed safe storage as ready for deletion
Success	202 (Accepted)	Retry later to get the result of the request
Failure	404 (Not Found)	Start all over with a storage commitment request
Failure	410 (Gone)	Start all over with a storage commitment request
*	Any other code	Do further analysis

N.8 Security

[This section contains several subsections that describe information that may already be present in other security documents (e.g., MDS2 statement). For each subsection, you can therefore either fill it in or remove it and reference a security document if all requested information is present in the referenced document.]

N.8.1 Introduction

The security section describes security features implemented by this product. It includes descriptions of non-DICOM network protocols, information to configure firewalls and application whitelists, lists of supported DICOM security profiles as well as Web Security features. Additionally, secured media storage, VPN, etc. are also specified in this security section.

N.8.2 External Network Requirements

Table N.8-1 describes additional non-DICOM network protocols that are used by <Product>.

[From this table, delete any Profiles/Actors/Transactions that are not supported at all.If the Profile is supported using a secure mechanism use Y for yes in the "Security Support" column, otherwise use N for No.]

Table N.8-1. External Network Requirements

Profile	Actor	Transaction	Protocol Used	RFCs	Reference
Basic Time Synchronization	NTP Server	Maintain Time	NTP	RFC5905; <<RFC5906 RFC8633>>	N.11.1.1
		Find NTP Servers	NTP	RFC5905; <<RFC5906 RFC8633>>	N.11.1.1
	NTP Client	Maintain Time	NTP	RFC5905; <<RFC5906 RFC8633>>	N.11.1.1
		Find NTP Servers	NTP	RFC5905; <<RFC5906 RFC8633>>	N.11.1.1
	SNTP Client	Maintain Time	SNTP	RFC2030	N.11.1.1
	DHCP Server	Find NTP Servers	DHCP	RFC2131; RFC2132; RFC2563	N.11.1.1
	DHCP Client	Find NTP Servers	DHCP	RFC2131; RFC2132; RFC2563	N.11.1.1
Basic Network Address Management	DHCP Server	Configure DHCP Server	-	-	N.11.1.2
		Find and Use DHCP Server	DHCP	RFC2131; RFC2132; RFC2563	N.11.1.2
		Maintain Lease	DCP	RFC2131; RFC2132	N.11.1.2
		Resolve Hostname	DNS	RFC1035; RFC2181	N.11.1.2
		DDNS Coordination	DNS	RFC2136	N.11.1.2
	DHCP Client	Find and Use DHCP Server	DHCP	RFC2131; RFC2132; RFC2563	N.11.1.2
		Maintain Lease	DHCP	RFC2131; RFC2132	N.11.1.2
	DNS Server	DNS Coordination	DNS	RFC2136; <<RFC4033 RFC4034 RFC4035>>	N.11.1.2
		Resolve Hostname	DNS	RFC1035; RFC2181; <<RFC4033 RFC4034 RFC4035>>	N.11.1.2
	DNS Client	Resolve Hostname	DNS	RFC1035; RFC2181; <<RFC4033 RFC4034 RFC4035>>	N.11.1.2
Application Configuration Management	LDAP Server	Query LDAP Server	LDAP	RFC2251	N.11.1.3
		Update LDAP Server	LDAP	RFC2251	N.11.1.3
		Maintain LDAP Server	LDAP	RFC2849	N.11.1.3
	LDAP Client	Find LDAP Server	LDAP	RFC2181; RFC2219; RFC2782	N.11.1.3
		Query LDAP Server	LDAP	RFC2251	N.11.1.3
		Update LDAP Server	LDAP	RFC2251	N.11.1.3
	DNS Server	Find LDAP Server	LDAP	RFC2181; RFC2219; RFC2782	N.11.1.3
DNS Service Discovery	DNS Server	Find DICOM Service	DNS	RFC2136; RFC2181; RFC2219; RFC2782; RFC6762; RFC6763; RFC8553; <<RFC4033 RFC4034 RFC4035>>	N.11.1.4
	DNS Client	Find DICOM Service	DNS	RFC2136; RFC2181; RFC2219; RFC2782; RFC6762; RFC6763; RFC8553; <<RFC4033 RFC4034 RFC4035>>	N.11.1.4
[Any additional profile]

N.8.3 TCP Port Configuration

See Section N.6 Configuration for information on the usage of ports for DICOM and other protocols. This section contains helpful information for product administrators to configure firewalls, application whitelists, etc.

[It is advised to make sure enough information is provided to support security configuration. For example, for Firewall configuration, list all other non-DICOM ports and/or provide a reference to any other security document that may be useful for the reader.]

N.8.4 DICOM Security Profiles Support

N.8.4.1 Secure Use and User Identity Profiles

Table N.8-2 lists the Secure Use and User Identity Profiles:

[In Table N.8-2 below, all the Profiles not supported can be deleted. But it is also permitted to keep them for transparency reasons and mark them with "N".]

Table N.8-2. Secure Use and User Identity Profiles

Profile	Creator/Sender	Consumer/Receiver	Reference
Online Electronic Storage Secure Use			N.11.2.1
Audit Trail Message Format			N.11.2.2
Audit Trail Message Transmission Profile - SYSLOG-TLS			N.11.2.3
Audit Trail Message Transmission Profile - SYSLOG-UDP			N.11.2.4
Basic User Identity Association			N.8.5
User Identity Plus Passcode Association			N.8.5
Kerberos Identity Negotiation Association			N.8.5
Generic SAML Assertion Identity Negotiation Association			N.8.5
[Any additional profile]

N.8.4.2 Secure Transport Connection Profiles

[In Table N.8-3 below, all the Profiles not supported can be deleted. But it is also permitted to keep them for transparency reasons and mark them with "N".

In the "Secured AE" column list the AEs that support the Profile (use ALL if all AEs support it, ALL EXCEPT to provide an exception list). In the "Sender" and "Receiver" columns, describe if the Profile is supported or not using Y or N.]

Table N.8-3 describes the Secure Transport Connection Profiles supported by the product. Accepted cipher suites are described in the section listed in the "Reference" column.

Table N.8-3. Secure Transport Connection Profiles

Profile	Secured AE	Sender	Receiver	Reference
BCP 195 RFC 8996 TLS Secure Transport Connection Profile				N.11.2.5
Modified BCP 195 RFC 8996 TLS Secure Transport Connection Profile				N.11.2.5
[Any additional or retired TLS Profile]

N.8.4.3 Media Storage Security Profiles

See Section N.1.4 Media Services for information on supported secured Application Profiles and secured media.

Table N.8-4 details the encryption mechanisms that are supported with secure media.

[In Table N.8-4, all the Profiles not supported can be deleted. But it is also permitted to keep them for transparency reasons and mark them with "N".]

Table N.8-4. Content Encryption used for Secured Media

Encryption	File Set Creator/File Set Updater	File Set Reader
AES
Triple-DES
[Other encryption]

[In Table N.8-5, all the Profiles not supported can be deleted. But it is also permitted to keep them for transparency reasons and mark them with "N".]

Table N.8-5. Content Types used for Secured Media

Content Types	File Set Creator/File Set Updater	File Set Reader
Signed-data
Digested-data
[Other content type]

[In Table N.8-6, all the Profiles not supported can be deleted. But it is also permitted to keep them for transparency reasons and mark them with "N".]

Table N.8-6. Digest Algorithms used for Secured Media

Digest Algorithms	File Set Creator/File Set Updater	File Set Reader
SHA-1
SHA256
SHA384
SHA512
[Other digest algorithm]

N.8.4.4 Attribute Confidentiality Profiles

Table N.8-7 lists supported Attribute Confidentiality Profiles and options:

[In Table N.8-7 all the Profiles not supported can be deleted. But it is also permitted to keep them for transparency Reasons and mark them with "N".

Add any private option and/or private profiles. For each option, indicate in the "AE" column the list of AEs that support the option (Use ALL if all AEs support it, ALL EXCEPT to provide an exception list). In remaining columns, indicate whether the option is supported as de-identifier, as re-identifier and if some configurability can be performed in the way anonymization can be applied.]

Table N.8-7. Attribute Confidentiality Profiles

Profile	Option	AE	De-identifier	Re-identifier	Configurable
Basic Application Level Confidentiality
	Basic Profile
	Clean Pixel Data
	Clean Recognizable Visual Features
	Clean Graphics
	Clean Structured Content
	Clean Descriptors
	Retain Longitudinal Temporal Information with Full Dates
	Retain Longitudinal Temporal Information with Modified Dates
	Retain Patient Characteristics
	Retain Device Identity
	Retain Institution Identity
	Retain UIDs
	Retain Safe Private
	[Additional option]
[Any Additional confidentiality profiles]	[Any option if applicable]

[Describe here the general strategy that applies to the product for new Attributes that could be defined later in the standard. Will they be kept, removed or can the behavior be configured? If configurable, does the configuration apply to all new elements or will it be configurable on a data element per data element basis?]

See Section N.11.2.6 for implementation details.

N.8.4.5 Digital Signature Profiles

[List here any Digital Signature Profile that your product may support. Also document the details of the supported profiles in Section N.11.2.7. Mark this section as N/A if your product does not support any Digital Signature profile.]

N.8.4.6 Additional DICOM Security Profiles

[List here any additional DICOM Security Profile that your product may support. Mark this section as N/A if your product does not support any additional profile.]

N.8.5 User Identity Negotiation Support

[If your product does not support any User Identity Negotiation, mark this section as N/A and delete subsections.]

N.8.5.1 Association Initiation

Table N.8-8 lists User Identity Negotiation support as Association Initiator:

[In the following table, if your product supports User Identity Negociation as an Association Initiator, use Y for yes in the "Supported" column, otherwise use N for No. For each supported field, indicate the list of values that are supported in the "Requested Value" column.]

Table N.8-8. User Identity Negotiation as Association Initiator

User Identity Negotiation

Supported

Requested Value

User-Identity-Type

<<1

5>>

Positive-response-requested

<<0

1>>

[If your product implements User Identity Negotiation without supporting a User Identity profile listed in Section N.8.4.1, describe here additional encryption, MAC and signature algorithms that your product supports beyond the minimal requirements specified in RFC 7519 (e.g., for support of JSON Web Token (JWT) - User identity type=5).]

N.8.5.2 Association Acceptance

Table N.8-9 lists User Identity Negotiation support as Association Acceptor:

[In the following table, if your product supports User Identity Negotiation as an Association Acceptor, use Y for yes in the "Supported" column and indicate the list of values that are supported in the "Requested Value" column, otherwise use N for No.]

Table N.8-9. User Identity Negotiation as Association Acceptor

User Identity Negotiation

Supported

Supported Value

User-Identity-Type

<<1

5>>

[Describe here how your product supports User Identity negotiation to authenticate the user and rules applied to this authentication. If this information is provided in an external document, provide the reference to this document in this section instead.]

N.8.6 Web Services Security Features

[Describe in this section the security mechanisms utilized by the implementation. In particular (but not limited to), consider:

Audit control mechanism used
Access authorizing policy and method, including details regarding trust methods, e.g., use of OAuth, use of access tokens, etc.
Personal authentication mechanisms
De-identification management
Certification management tools and process
Web server attack handling

These descriptions may be just a reference to another section of the Conformance Statement if these mechanisms are common with DICOM networking services described before or may contain references to other relevant documentation.]

N.8.7 Other Security Features

[Describe in the following subsections any additional security features not covered in previous sections that your product may support.]

N.8.7.1 Media Storage Security

[Describe here any support of additional media storage security features such as encrypted media. Put "N/A" if none.]

N.8.7.2 Network Security

[Describe here any support additional network security features such as VPN, etc. Put "N/A" if none.]

N.8.7.3 Other Security Features

[Describe here any additional supported security features not described in previous sub-sections such as physical security features (access card, tokens, two factor authentications, OAuth, IHE IUA Profile etc.). If available, you can also provide a link to MDS2 statements applicable to the various AEs of this product here. Put "N/A" if none.]

Annexes

[In an actual DICOM Conformance Statement Section N.9 to Section N.13 should be numbered Annex A to Annex E.]

N.9 A.A Information Object Definitions (IODs)

[Note that the Annexes defined in the following subsections are a mandatory part of the DICOM Conformance Statement and must be filled for any product that creates DICOM objects.]

[For all SOP Instances of supported Storage SOP Classes (including Real-Time Video objects) that can be created by the system (see Overview Section N.1.1) provide an Annex A.x.]

[Throughout all the tables in this Annex, the Tag order is as it appears in the DICOM Standard to ease comparison and validation. It is recommended that products do the same in their Conformance Statements.]

This section describes all the SOP Instances natively created by <Product>, e.g., images created by an acquisition modality or evidence documents created on a review workstation (i.e., all SOP Classes that are marked in the "Created" column in Table N.1-1). Details on Attribute coercion are defined in Section N.5.2.5.2.

In the "Source" column, the following Values can be used:

FIXED: The Value is pre-defined and cannot be modified.
GENERATED: The Value is generated by the system.
CONFIGURATION: The Value is copied from the system configuration.
MWL: The Value is copied from a Modality Worklist entry.
QUERY: The Value is determined by performing a query of any of the supported Query/Retrieve Services.
USER: The Value is entered by the user.
SCANNED: The Value is read from a barcode scanner or similar device.
EMPTY: The Attribute is sent with a zero-length Value.
SRC_INSTANCE: The Value is copied from previously created/received SOP Instances.

The "Presence" columns reflect the usage of the Module, Functional Group Macro, Attributes, or Value in the <product>Implementation and is not necessarily the same as defined in the DICOM Standard. For the "Presence" column the following Values can be used:

ALWAYS: the module, functional group macro, Attributes or Value is always present.
CONDITIONAL: the presence of the module, functional group macro, Attributes or Value is dependent on a condition. The condition must be listed in the "Conditions" column.
SRC_COPY: The presence of the Attributes and Values depends on the availability of these in the source instances, which are used for copying this information.
EMPTY: The Attribute is present but without a Value (zero length).

N.9.1 A.A.1 Information Shared Across Multiple IODs

N.9.1.1 A.A.1.1 Common Modules

All SOP Instances generated by the system use the common modules listed in Table N.9-1 to Table N.9-12 or a subset of them, as defined in the IOD specific subsections below.

[The tables list the most common Modules; tables for additional Modules can be appended at the end. It is up to the editor of the DICOM Conformance Statement to move some of the tables to the IOD specific sections, if the information differs between the documented IODs.]

[Complete the following tables and provide information on all Attributes that are populated in your IOD, add additional Attributes, remove Attributes not used and provide a description how the Attributes are populated.]

[For the "Source" column use one of the pre-defined terms above, also note that multiple Values are allowed, however an explanation of the conditions under which one or the other Value is used, must be provided.]

[If in the "Value" column different Values are supported, they can be defined in the Shared Values and Code Set subsection and a reference to the respective table can be entered in the "Value" column. Furthermore, for Coded Terms it is possible to provide a reference to a CID defined in PS3.16.]

[For the "Presence" columns the Values defined above can be used. Also note that multiple Values are allowed, however an explanation of the conditions under which one or the other Value is used, must be provided.]

[If the modules use Attributes that can support different Value Types (See PS3.15), add the Value Type supported in the "Comments" column.]

Table N.9-1. Patient Module

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
Patient's Name	(0010,0010)	MWL; USER	ALWAYS	CONDITIONAL		Value empty if unidentified Patient	See Section N.12
…

Table N.9-2. General Study Module

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
Study Instance UID	(0018,000D)	MWL;GENERATED	ALWAYS	ALWAYS
Study Date	(0008,0020)	GENERATED	ALWAYS	ALWAYS	Current Date
Accession Number	(0008,0050)	MWL;EMPTY	ALWAYS				See Section N.12
…
Requesting Service Code Sequence	(0032,1034)	MWL; CONFIGURATION	ALWAYS	ALWAYS	See Section N.9.1.4	Copied from MWL or read from Configuration File
…

Table N.9-3. General Series Module

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value
Modality	(0008,0060)	FIXED	ALWAYS	ALWAYS	CT
Series Instance UID	(0020,000E)	GENERATED	ALWAYS	ALWAYS
…

Table N.9-4. Frame of Reference Module

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
…

Table N.9-5. General Equipment Module

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
…

Table N.9-6. Enhanced General Equipment Module

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments

Table N.9-7. General Image Module

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
…

Table N.9-8. Image Pixel Module

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
Photometric Interpretation	(0028,0004)	GENERATED	ALWAYS		See Section N.9.1.4
…

Table N.9-9. Multi-Frame Functional Groups Module

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
Shared Functional Groups Sequence	(5200,9229)
> [ Include one or more Functional Group Macros documented in Section A.1.2 or in IOD specific subsections]
Per-frame Functional Groups Sequence	(5200,9230)
> [Include one or more Functional Group Macros documented in Section A.1.2 or in IOD specific subsections]
…

Table N.9-10. Multi-Frame Dimension Module

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
…

Table N.9-11. Acquisition Context Module

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
…

Table N.9-12. SOP Common Module

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
SOP Class UID	(008,0016)	GENERATED	ALWAYS	ALWAYS			Value matches SOP Class of generated object
SOP Instance UID	(0008,0018)	GENERATED	ALWAYS	ALWAYS
Specific Character Set	(0008,0005)	CONFIGURATION	CONDITIONAL	ALWAYS	See Section N.5.7	Required if any Character Set other than ISO_IR 100 is used
…
Private Data Element Characteristics Sequence	(0008,0300)	GENERATED	CONDITIONAL	CONDITIONAL	Only present in IODs that use private data elements	Used if IOD contains private Attributes
>>…

[If your product uses other Modules that are shared between multiple IODs created on your product, list them in tables following the structure of the above ones.]

N.9.1.2 A.A.1.2 Common Functional Group Macros

The tables below list the Common Functional Group Macros that can either be used as part of the Shared Functional Groups Sequence (5200,9229) or as part of the Per-frame Functional Groups Sequence (5200,9230) of enhanced image IODs.

[Modify/add/delete tables below to match your product implementation. For content of the columns, see the instructions in A.1.1 Common Modules:

Add Macros that are not listed, but used in IODs generated by your product
Remove Macros that are not used by any of your IODs
Modify/Add the Attributes as needed

If you do not create any enhanced IODs mark this section as N/A, append "-N/A" to the Section Title and remove the tables below.]

Table N.9-13. Pixel Measures Functional Group Macro

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
Pixel Measures Sequence	(0028,9110)
>Pixel Spacing	(0028,0030)
>Slice Thickness	(0018,0050)
>Spacing Between Slices	(0018,0088)

Table N.9-14. Frame Content Functional Group Macro

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
Frame Content Sequence	(0020,9111)

Table N.9-15. Plane Position (Patient) Functional Group Macro

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
Plane Position Sequence	(0020,9113)

Table N.9-16. Plane Orientation (Patient) Functional Group Macro

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
Plane Orientation Sequence	(0020,9116)

Table N.9-17. Referenced Image Functional Group Macro

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
Referenced Image Sequence	(0008,1140)

Table N.9-18. Frame Anatomy Functional Group Macro

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
Frame Anatomy Sequence	(0020,9071)

Table N.9-19. Irradiation Event Identification Functional Group Macro

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
Irradiation Event Identification Sequence	(0018,9477)

N.9.1.3 A.A.1.3 Common Private Modules

The tables below list private Attributes that are used in multiple IODs generated by the system. For documentation convenience and readability, they are organized in modules, although the concept of modules does not exist in the standard for private Attributes.

[For each Common Private Module create a table following the structure listed below and populate it with all private Attributes which are shared between different IODs. For each Attribute list name, Tag, Value Representation, Value Multiplicity, whether the Value contains Identifiable Information). In the "Identifiable Information" column the following Values can be used: SAFE, UNSAFE, MIXED. For details see the Private Data Element Characteristics Sequence (0008,0300) as defined in DICOM PS3.3.

For the other columns see the instructions above. It is highly recommended to populate the Private Data Element Characteristics Sequence (0008,0300) if Private Attributes are being used.]

[For a description of the purpose of the Private Attribute either use the "Comments" column or add a note below the table.]

Table N.9-20. Private Module 1

Attribute Name	Tag	VR	VM	Identifiable Information	Presence of Value	Value	Conditions
Private Creator	(0009,00xx)	LO	1		ALWAYS	PRIVATEDATA1
Private Attribute 1	(0009,xx01)	CS	1		ALWAYS	VALUE1
Private Attribute 2	(0009,xx02)	IS	1-n	SAFE	CONDITIONAL	35\27\45	(0009,xx01) = VALUE1

Table N.9-21. Private Module 2

Attribute Name	Tag	VR	VM	Value
Private Creator	(0029,00xx)	LO	1	PRIVATEDATA2
Private Attribute 3	(0029,xx01)	DT	1
Private Attribute 4	(0029,xx02)	TM	1

N.9.1.4 A.A.1.4 Coded Values

Table N.9-22 lists Coded Values referenced from the "Value" column of the tables above.

[Document Coded Terms and Code String values in the following table. Coded Terms must be documented as (Code Value, Coding Scheme Designator, "Code Meaning".]

Table N.9-22. Values and Code Sets shared across IODs

Attribute Name	Tag	Value/Code	Condition
Requesting Service Code Sequence	(0032,1034)	(309915006, SCT, "Cardiology")
Requesting Service Code Sequence	(0032,1034)	(309964003, SCT, "Radiology")
Photometric Interpretation	(0028,0004)	MONOCHROME1	Grayscale Images
		YBR_FULL_422	JPEG compressed Images
		RGB	Uncompressed color images

N.9.2 A.A.2 <image IOD1 E.g. Computed Tomography Image IOD>

Table N.9-23 defines the structure of <Image IOD 1>.

[Provide a list of all Modules, their presence, conditions in which they will be present and a reference to a table with the detailed module description. Below is an example for a CT Image IOD.]

Table N.9-23. <Image IOD 1>

IE	Module Name	Presence (Module)	Condition	Reference
Patient	Patient Module	ALWAYS		Table N.9-1
Study	General Study Module	ALWAYS		Table N.9-2
Series	General Series Module	ALWAYS		Table N.9-3
Frame Of Reference	Frame of Reference	ALWAYS		Table N.9-4
Equipment	General Equipment Module	ALWAYS		Table N.9-5
Image	General Image Module	ALWAYS		Table N.9-7
	Image Plane Module	ALWAYS		Table N.9-24
	CT Image	ALWAYS		Table N.9-25
	Image Pixel Module	ALWAYS		Table N.9-8
	SOP Common Module	ALWAYS		Table N.9-12
	Private Module 1	CONDITIONAL	Present for Acquisition Protocol XXX	Table N.9-20
	Private Module 2	ALWAYS		Table N.9-21
	Private Module 3	ALWAYS		Table N.9-26

N.9.2.1 A.A.2.1 <Image IOD 1> Specific Modules

The following tables list Modules and Attributes specific for <Image IOD 1>:

[List all IOD specific Modules in a separate table following the structure defined below, their Attributes, Values, usage, and conditions in the table below. For instructions on the content of the columns see instructions in SectionA.A Information Object Definitions (IODs).]

Table N.9-24. Image Plane Module for <Image IOD 1>

Attribute Name	Tag	Source
Pixel Spacing	(0028,0030)	GENERATED
Image Orientation (Patient)	(0020,0037)	GENERATED
Image Position (Patient)	(0020,0032)	GENERATED
Slice Thickness	(0018,0050)	GENERATED

Table N.9-25. CT Image Module for <Image IOD 1>

Attribute Name	Tag	Source	Value
Image Type	(0008,0008)	GENERATED	See section A.2.4
Samples per Pixel	(0028,0002)	GENERATED	1
Photometric Interpretation	(0028,0004)	GENERATED	MONOCHROME2
Bits Allocated	(0028,0100)	GENERATED	16
Bits Stored	(0028,0101)	GENERATED	12
High Bit	(0028,0102)	GENERATED	11
Rescale Intercept	(0028,1052)	GENERATED	1024
Rescale Slope	(0028,1053)	GENERATED
KVP	(0018,0060)	GENERATED
Acquisition Number	(0020,0012)	GENERATED
Exposure Time	(0018,1150)	GENERATED
X-Ray Tube Current	(0018,1151)	GENERATED
Exposure	(0018,1152)	GENERATED
Anatomic Region Sequence	(0008,2218)	GENERATED	See CID 4 "Anatomic Region"

N.9.2.2 A.A.2.2 <Image IOD 1> Functional Group Macros - NA

N/A

N.9.2.3 A.A.2.3 <Image IOD 1> Private Modules

Table N.9-26 lists private Modules and Attributes for < Image IOD 1>:

[List all private Attributes added specifically for this IOD here. Mark this section as N/A if there are none. If the description gets too long, you can add footnotes under the table.]

Table N.9-26. Private Module3 for <Image IOD 1>

Attribute Name	Tag	VR	VM	Identifiable Information	Presence of Attribute	Presence of Value	Value
Private Creator	(0039,00xx)	LO	1			ALWAYS	PRIVATEDATA3
Private Attribute 5	(0039,xx01)	CS	1	SAFE	ALWAYS	ALWAYS	VALUE1
…

N.9.2.4 A.A.2.4 <Image IOD 1> Coded Values

Table N.9-27 lists Coded Values referenced from the "Value" column of the tables above for <Image IOD 1>:

[Document Coded Terms and Code String values in the following table. Coded Terms must be documented as (Code Value, Coding Scheme Designator, "Code Meaning".]

Table N.9-27. Values and Code Sets for <Image IOD 1>

Attribute Name	Tag	Value/Code	Condition
Image Type	(0008,0008)	ORIGINAL DERIVED	Value for Value 1
		PRIMARY SECONDARY	Value for Value 2
		AXIAL	Value for Value 3
		VMI ELECTRON_DENSITY	Value for Value 4
		…

N.9.3 A.A.3 <image IOD 2 E.g., Enhanced Computed Tomography Image IOD>

Table N.9-28 defines the structure of <Image IOD 2>.

[Provide a list of all Modules, their presence, conditions in which they will be present and a reference to a table with the detailed module description. Below is an example for a Enhanced Computed Tomography Image IOD.]

Table N.9-28. <Image IOD 2>

IE	Module Name	Presence (Module)	Reference
Patient	Patient Module	ALWAYS	Table N.9-1
Study	General Study Module	ALWAYS	Table N.9-2
Series	General Series Module	ALWAYS	Table N.9-3
Series	CT Series Module	ALWAYS	Table N.9-30
Frame of Reference	Frame of Reference	ALWAYS	Table N.9-4
Equipment	General Equipment Module	ALWAYS	Table N.9-5
Equipment	Enhanced General Equipment	ALWAYS	Table N.9-6
Image	Image Pixel	ALWAYS	Table N.9-8
	Multi-Frame Functional Groups	ALWAYS	Table N.9-9
	Multi-Frame Dimension	ALWAYS	Table N.9-10
	Acquisition Context	ALWAYS	Table N.9-11
	Enhanced CT Image	ALWAYS	Table N.9-31
	SOP Common Module	ALWAYS	Table N.9-12

Table N.9-29 lists the Functional group macros used in <Image IOD2>. The "Usage" column defines whether a Macro is used as a shared Macro, on a per frame base or whether depending on the acquisition context can be used in both contexts. The following Values are supported:

PER_FRAME: The macro is used on a per frame basis, the Attributes are included in the Per-frame Functional Groups Sequence (5200,9230)
SHARED: The macro is shared across all frames; the Attributes are included in the Shared Functional Groups Sequence (5200,9229)
CONTEXT_DEPENDENT: Depending on the acquisition context the macro can either be used on a per frame basis or be shared across all frames.

[Provide a list of all functional group macros, their presence, conditions in which they will be present and a reference to a table with the detailed macro description.]

Table N.9-29. Functional Group Macros used in < Image IOD 2>

Functional Group Macro	Presence	Condition	Usage	Reference
Pixel Measures	ALWAYS		PER_FRAME	Table N.9-13
Frame Content	ALWAYS		PER_FRAME	Table N.9-14
Plane Position (Patient)	ALWAYS		SHARED	Table N.9-15
Frame Anatomy	ALWAYS		CONTEXT_DEPENDENT	Table N.9-18
Irradiation Event Identification	ALWAYS		PER_FRAME	Table N.9-19
CT Image Frame Type	ALWAYS		PER_FRAME	Table N.9-32
CT Acquisition Type	CONDITIONAL	For images with Image Type (0008,0008) Value 1 as ORIGINAL or MIXED	SHARED	Table N.9-33
CT Acquisition Details	CONDITIONAL	For images with Image Type (0008,0008) Value 1 as ORIGINAL or MIXED	SHARED	Table N.9-34
CT Table Dynamics	CONDITIONAL	For images with Image Type (0008,0008) Value 1 as ORIGINAL or MIXED	SHARED	Table N.9-35
CT Position	CONDITIONAL	For images with Image Type (0008,0008) Value 1 as ORIGINAL or MIXED	SHARED	Table N.9-36
CT Geometry	CONDITIONAL	For images with Image Type (0008,0008) Value 1 as ORIGINAL or MIXED	SHARED	Table N.9-37
CT Reconstruction	CONDITIONAL	For images with Image Type (0008,0008) Value 1 as ORIGINAL or MIXED	SHARED	Table N.9-38.
CT Exposure	CONDITIONAL	For images with Image Type (0008,0008) Value 1 as ORIGINAL or MIXED	SHARED	Table N.9-39
CT X-Ray Details	CONDITIONAL	For images with Image Type (0008,0008) Value 1 as ORIGINAL or MIXED	SHARED	Table N.9-40
CT Pixel Value Transformation	ALWAYS		SHARED	Table N.9-41
CT Additional X-Ray Source	CONDITIONAL	For systems with multiple X-Ray sources	SHARED	Table N.9-42
Multi-energy CT Characteristics	CONDITIONAL	For systems with multiple X-Ray sources	SHARED	Table N.9-43
..

N.9.3.1 A.A.3.1 <Image IOD 2> Specific Modules

The following tables list Modules and Attributes specific for <Image IOD 2>:

Table N.9-30. CT Series Module for <Image IOD 2>

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments

Table N.9-31. Enhanced CT Image Module for <Image IOD 2>

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments

N.9.3.2 A.A.3.2 <Image IOD 2> Functional Group Macro

The tables below list functional group macros and Attributes for <Image IOD 2>:

[For enhanced objects provide the list of IOD specific shared Functional Group Macros and per-frame Functional Group Macros. Create one table for each supported Functional Group Macro using the structure defined below.]

Table N.9-32. CT Frame Type Functional Group Macro for <Image IOD 2>

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
CT Image Frame Type Sequence	(0018,9329)
…

Table N.9-33. CT Acquisition Type Functional Group Macro for <Image IOD 2>

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
CT Acquisition Type Sequence	(0018,9301)

Table N.9-34. CT Acquisition Details Functional Group Macro for <Image IOD 2>

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
CT Acquisition Details Sequence	(0018,9304)

Table N.9-35. CT Table Dynamics Functional Group Macro for <Image IOD 2>

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
CT Table Dynamics Sequence	(0018,9308)

Table N.9-36. CT Position Functional Group Macro for < Image IOD 2>

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
CT Position Sequence	(0018,9326)

Table N.9-37. CT Geometry Functional Group Macro for <Image IOD 2>

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
CT Geometry Sequence	(0018,9312)

Table N.9-38. CT Reconstruction Functional Group Macro for <Image IOD 2>

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
CT Reconstruction Sequence	(0018,9314)

Table N.9-39. CT Exposure Functional Group Macro for <Image IOD 2>

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
CT Exposure Sequence	(0018,9321)

Table N.9-40. CT X-Ray Details Functional Group Macro for <Image IOD 2>

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
CT X-Ray Details Sequence	(0018,9325)

Table N.9-41. CT Pixel Value Transformation Functional Group Macro for <Image IOD 2>

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
Pixel Value Transformation Sequence	(0028,9145)

Table N.9-42. CT Additional X-Ray Source Functional Group Macro for <Image IOD 2>

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
CT Additional X-Ray Source Sequence	(0018,9360)

Table N.9-43. CT Multi-energy CT Characteristics Functional Group Macro for <Image IOD 2>

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions	Comments
Multi-energy CT Processing Sequence	(0018,9363)

N.9.3.3 A.A.3.3 <Image IOD 2> Private Modules

[List all private Attributes added specifically for this IOD here. Mark this section as N/A if there are none.]

N.9.3.4 A.A.3.4 <Image IOD 2> Coded Values

Table N.9-44 lists Coded Values referenced from the "Value" column of the tables above for <Image IOD 2>:

[Document Coded Terms and Code String values in the following table. Coded Terms must be documented as (Code Value, Coding Scheme Designator, "Code Meaning".]

Table N.9-44. Values and Code Sets for <Image IOD 2>

Attribute Name	Tag	Value/Code	Condition	Comments

N.9.4 A.A.4. <SR IOD 1 E.g., Comprehensive SR IOD>

Table N.9-45 defines the structure of <SR IOD 1>.

[Provide a list of all Modules, their presence, conditions in which they will be present and a reference to a table with the detailed module description. Below is an example for a Comprehensive SR IOD.]

Table N.9-45. <SR IOD 1>

IE	Module Name	Presence (Module)	Reference
Patient	Patient Module	ALWAYS	Table N.9-1
Study	General Study Module	ALWAYS	Table N.9-2
Series	SR Document Series Module	ALWAYS	Table N.9-47
Equipment	General Equipment Module	ALWAYS	Table N.9-5
Document	SR Document General Module	ALWAYS	Table N.9-47
	SR Document Content	ALWAYS	Table N.9-48
	SOP Common Module	ALWAYS	Table N.9-12

N.9.4.1 A.A.4.1 <SR IOD 1> Specific Modules

The tables below list modules and Attributes used in <SR IOD1>:

[List all IOD specific Modules in a separate table following the structure defined below, their Attributes, Values, usage, and conditions in the Table below. For instructions on the content of the columns see instructions in SectionA.A Information Object Definitions (IODs).]

Table N.9-46. SR Document Series Module used in <SR IOD 1>

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions
Modality	(0008,0060)	FIXED		ALWAYS	SR
Referenced Performed Procedure Step Sequence	(0008,1111)	GENERATED	ALWAYS	CONDITIONAL	(See Section N.12 for details)	See Section N.12
..

Table N.9-47. SR Document General Module used in <SR IOD 1>

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value	Conditions
Completion Flag	(0040,A491)	GENERATED	ALWAYS	ALWAYS	<<PARTIAL COMPLETE>>
Verification Flag	(0040,A493)	GENERATED	ALWAYS	ALWAYS	<<UNVERIFIED VERIFIED>>
Content Date	(0008,0023)	GENERATED	ALWAYS	ALWAYS	Current date
Content Time	(0008,0033)	GENERATED	ALWAYS	ALWAYS	Current time
Referenced Request Sequence	(0040,A370)	GENERATED	ALWAYS	CONDITIONAL	See Section N.12	See Section N.12
…

Table N.9-48. SR Document Content Module used in <SR IOD 1>

Attribute Name	Tag	Source	Presence of Attribute	Presence of Value	Value
Value Type	(0040,A040)	FIXED	ALWAYS	ALWAYS	CONTAINER
Continuity of Content	(0040,A050)	FIXED	ALWAYS	ALWAYS	SEPARATE
Content Template Sequence	(0040,A504)	GENERATED	ALWAYS	ALWAYS	See Section N.10 for encoding on supported TIDs

N.9.4.2 A.A.4.2 <SR IOD 1> Functional Group Macros - N/A

N/A

N.9.4.3 A.A.4.3 <SR IOD 1> Private Modules

[List all private Attributes added specifically for this IOD here. Mark this section as N/A if there are none.]

N.9.4.4 A.A.4.4 <SR IOD 1> Coded Values

Table N.9-49 lists Coded Values referenced from the "Value" column of the tables above for <SR IOD1>:

[Document Coded Terms and Code Stringe values in the following table. Coded Terms must be documented as (Code Value, Coding Scheme Designator, "Code Meaning".]

Table N.9-49. SR IOD 1>

Attribute Name	Tag	Value/Code	Condition	Comments

N.9.5 A.A.5 Basic Directory IOD

Table N.9-50 defines the structure of the Basic Directory IOD.

Table N.9-50. Basic Directory IOD

Attribute Name	Tag	Source
File Set Identification Module
File-set ID	(0004,1130)	GENERATED
Specific Character Set of File-set Descriptor File	(0004,1142)	GENERATED
Directory Information Module
Offset of the First Directory Record of the Root Directory Entity	(0004,1200)	GENERATED
Offset of the Last Directory Record of the Root Directory Entity	(0004,1202)	GENERATED
File-set Consistency Flag	(0004,1212)	GENERATED
Directory Record Sequence	(0004,1220)	GENERATED
>Offset of the Next Directory Record	(0004,1400)	GENERATED
>Record In-use Flag	(0004,1410)	GENERATED
>Offset of Referenced Lower-Level Directory Entity	(0004,1420)	GENERATED
>Directory Record Type	(0004,1430)	GENERATED
>Referenced File ID	(0004,1500)	GENERATED
>Referenced SOP Class UID in File	(0004,1510)	SRC_INSTANCE
>Referenced SOP Instance UID in File	(0004,1511)	SRC_INSTANCE
>Referenced Transfer Syntax UID in File	(0004,1512)	SRC_INSTANCE

Patient Keys
>Specific Character Set	(0008,0005)	GENERATED
>Patient's Name	(0010,0010)	SRC_INSTANCE
>Patient ID	(0010,0020)	SRC_INSTANCE
…
Study Keys
>Study Date	(0008,0020)	SRC_INSTANCE
>Study Time	(0008,0030)	SRC_INSTANCE
>Study Description	(0008,1030)	SRC_INSTANCE
>Study Instance UID	(0020,000D)	SRC_INSTANCE
>Study ID	(0020,0010)	SRC_INSTANCE
>Accession Number	(0008,0050)	SRC_INSTANCE
…
Series Keys
>Specific Character Set	(0008,0005)	GENERATED
>Modality	(0008,0060)	SRC_INSTANCE
>Series Instance UID	(0020,000E)	SRC_INSTANCE
>Series Number	(0020,0011)	SRC_INSTANCE
…
Image Keys
>Specific Character Set	(0008,0005)	GENERATED
>Instance Number	(0020,0013)	SRC_INSTANCE
>Samples per Pixel	(0028,0002)	SRC_INSTANCE
>Photometric Interpretation	(0028,0004)	SRC_INSTANCE
>Rows	(0028,0010)	SRC_INSTANCE
>Columns	(0028,0011)	SRC_INSTANCE
>Bits Allocated	(0028,0100)	SRC_INSTANCE
>Bits Stored	(0028,0101)	SRC_INSTANCE
>High Bit	(0028,0102)	SRC_INSTANCE
>Pixel Representation	(0028,0103)	SRC_INSTANCE
…
SR Document Keys
>Specific Character Set	(0008,0005)	GENERATED
>Instance Number	(0020,0013)	SRC_INSTANCE
>Completion Flag	(0040, A491)	SRC_INSTANCE
>Verification Flag	(0040, A493)	SRC_INSTANCE
>Content Date	(0008,0023)	SRC_INSTANCE
>Content Time	(0008,0033)	SRC_INSTANCE
>Verification DateTime	(0040,A030)	SRC_INSTANCE
>Concept Name Code Sequence	(0040,A043)	SRC_INSTANCE
>>Code Value	(0008,1000)
>>Coding Scheme Designator	(0008,1002)
>>Coding Scheme Version	(0008,1003)
>>Code Meaning	(0008,1004)

N.9.6 A.A.6 <Private IOD 1>

Table N.9-51 defines the structure of <Private IOD 1>.

[Provide a list of all Modules, their presence, conditions in which they will be present and a reference to a table with the detailed module description. Below is an example for a Private IOD.]

Table N.9-51. <Private IOD 1>

IE	Module Name	Presence (Module)	Condition	Reference
Patient	Patient Module	ALWAYS		Table N.9-1
Study	General Study Module	ALWAYS		Table N.9-2
Series	General Series Module	ALWAYS		Table N.9-3
Frame of Reference	Frame of Reference	ALWAYS		Table N.9-4
Equipment	General Equipment Module	ALWAYS		Table N.9-5
	Private Module 1	CONDITIONAL	Present for Acquisition Protocol XXX	Table N.9-20
	Private Module 2	ALWAYS		Table N.9-21
	Private Module 4	ALWAYS		Table N.9-52
	Private Module 5	ALWAYS		Table N.9-54
Image	SOP Common Module	ALWAYS		Table N.9-12

N.9.6.1 A.A.6.1 <Private IOD 1> Specific Modules - NA

N/A

N.9.6.2 A.A.6.2 <Private IOD 1> Functional Group Macros

[For <Private IODs> provide the list of shared Functional Group Macros and per-frame Functional Group Macros. Create one table for each supported Functional Group Macro using the structure defined below.]

N.9.6.3 A.A.6.3 <Private IOD 1> Private Modules

The tables below list Private Modules and Attributes specific for <Private IOD 1>:

Table N.9-52. Private Module 4 for <Private IOD 1>

Attribute Name	Tag	VR	VM	Identifiable Information	Value
Private Module 4
Private Creator	(0035,00xx)	LO	1
Private Attribute 6	(0035,xx01)	CS	1	SAFE	PRIVATECREATOR
					TERM1

Table N.9-53. Private Module 5 for <Private IOD 1>

Attribute Name	Tag	VR	VM	Identifiable Information	Value
Private Module 5
Private Creator	(0039,00yy)	LO	1		PRIVATECREATOR5
Private Attribute 7	(0039,yy01)	CS	1	UN SAFE	See Table N.9-54

N.9.6.4 A.A.6.4 <Private IOD 1> Coded Values

Table N.9-54 lists Coded Values referenced from the "Value" column of the tables above for <Private IOD 1>:

[Document Coded Terms and Code String values in the following table. Coded Terms must be documented as (Code Value, Coding Scheme Designator, "Code Meaning".]

Table N.9-54. Values and Code Sets for <Private IOD 1>

Attribute Name	Tag	Value/Code	Condition
Private Attribute 7	(0039,yy01)	TERM1	Color Image
Private Attribute 7	(0039,yy01)	TERM2	Grayscale Image

N.10 A.B Structured Report Content Encoding

[Note that the appendices defined in the following subsections are a mandatory part of the DICOM Conformance Statement and must be filled in by any product, that creates DICOM SR objects.]

[For each SR TID (including Private TIDs) that is created by the system (See Overview Section N.1.1.1) provide an Annex B.x.]

[If you are extending a TID by adding additional concepts indicate this extension by adding an asterisk to the TID number in the TID column (e.g.,4000*).]

[If your product creates SR Instances of a TID which includes long lists of measurements, they can also be documented in an external file. For details refer to the instructions right before Section N.10.2.]

This section provides the detailed content encoding for all TIDs supported by <product>.

Throughout the tables listed in Section N.10 the following codes are used for the "Source" and "Presence of Content Item" columns.

In the "Source" column, the following Values can be used:

FIXED: The Value is pre-defined and cannot be modified.
GENERATED: The Value is generated by the system.
CONFIGURATION: The Value is copied from the system configuration.
MWL: The Value is copied from a Modality Worklist entry.
QUERY: The Value is determined by performing a query of any of the supported Query/Retrieve Services.
USER: The Value is entered by the user.
SCANNED: The Value is read from a barcode scanner or similar device.
EMPTY: The Attribute is sent with a zero-length Value.
SRC_INSTANCE: The Value is copied from previously created/received SOP Instances.

In the "Presence of Content Item" the following Values can be used:

ALWAYS: the module, functional group macro, Attributes or Value is always present.
CONDITIONAL: the presence of the module, functional group macro, Attributes or Value is dependent on a condition. The condition must be listed in the "Comments" column.
SRC_COPY: The presence of the Attributes and Values depends on the availability of these in the source instances, which are used for copying this information.
EMPTY: The Attribute is present but without a Value (zero length).

N.10.1 A.B.1 Mammography CAD SR (TID 4000)

Table N.10-1 shows the encoding of content of a DICOM Mammography CAD SR (TID 4000).

[The following table shows how to document TID content usage, with TID 4000 as an example. Modify to match your product implementation, e.g., select supported concepts and Values and add additional templates as needed. In the "Value" column you can either list the coded Values directly, reference a CID from DICOM PS3.16 if used unmodified or provide a table in Section N.10.1.1, if you are using more than two codes (otherwise codes can be added directly to the table). For more complex TIDs it is possible to split the table below into multiple tables following the Template Structure defined in DICOM PS 3.16.]

Table N.10-1. Mammography CAD SR (TID 4000)

NL	Rel with Parent	VT	Concept Name	Source	Values	TID
		CONTAINER	(111036, DCM, "Mammography CAD Report")			4000
>	HAS CONCEPT MOD	CODE	(121049, DCM, "Language of Content Item and Descendants")	CONFIGURATION	(en, RFC3066, "English")	1204
>>	HAS CONCEPT MOD	CODE	(121046, DCM, "Country of Language")	CONFIGURATION	(US, ISO3166_1, "United States of America (the) ")	1204

>	CONTAINS	CONTAINER	(111028, DCM, "Image Library")			4020
>>	CONTAINS	IMAGE				4020
>>>	HAS ACQ CONTEXT	CODE	(111027, DCM, "Image Laterality")	SRC_INSTANCE	See CID 6023 "Side"	4020
>>>	HAS ACQ CONTEXT	CODE	(111031, DCM, "Image View")	SRC_INSTANCE	See CID 4014 "View for Mammography"	4020
>>>>	HAS CONCEPT MOD	CODE	(111032, DCM, "Image View Modifier")	SRC_INSTANCE	See Table N.10-2	4020
>>>	HAS ACQ CONTEXT	TEXT	(111044, DCM, "Patient Orientation Row")	SRC_INSTANCE		4020
>>>	HAS ACQ CONTEXT	TEXT	(111043, DCM, "Patient Orientation Column")	SRC_INSTANCE		4020
>>>	HAS ACQ CONTEXT	DATE	(111060, DCM, "Study Date")	SRC_INSTANCE		4020
>>>	HAS ACQ CONTEXT	TIME	(111061, DCM, "Study Time")	SRC_INSTANCE		4020
>>>	HAS ACQ CONTEXT	DATE	(111018, DCM, "Content Date")	SRC_INSTANCE		4020
>>>	HAS ACQ CONTEXT	TIME	(111019, DCM, "Content Time")	SRC_INSTANCE		4020
>>>	HAS ACQ CONTEXT	NUM	(111026, DCM, "Horizontal Pixel Spacing")	SRC_INSTANCE		4020
>>>	HAS ACQ CONTEXT	NUM	(111066, DCM, "Vertical Pixel Spacing")	SRC_INSTANCE		4020
>	CONTAINS	CODE	(111017, DCM, "CAD Processing and Findings Summary")	GENERATED	See CID 6047 "CAD and Processing Findings Summary"	4001
>>	HAS PROPERTIES	TEXT	(111033, DCM, "Impression Description")	GENERATED	(Description, e.g., Breast density evaluation)	4002
>>	HAS PROPERTIES	TEXT	(111001, DCM, "Algorithm Name")	GENERATED	(Algorithm Name, e.g., Breast Density Assessment)	4019
>>	HAS PROPERTIES	TEXT	(111003, DCM, "Algorithm Version")	GENERATED	(Version, e.g., 1.1.1.1)	4019
>>	HAS PROPERTIES	NUM	See CID 6142 Calculated Value	GENERATED		4002
>>>	HAS CONCEPT MOD	CODE	(272741003, SCT, "Laterality")	GENERATED	See CID 6023 "Side"	4002
>>>	HAS CONCEPT MOD	CODE	(121401, DCM, "Derivation")	GENERATED	See CID 6140 "Calculation Mehtod"	4002
>>	INFERRED FROM	CONTAINER	(111034, DCM, "Individual Impression/ Recommendation")	GENERATED		4003
>>>	HAS CONCEPT MOD	CODE	(111056, DCM, "Rendering Intent")	GENERATED	See CID 6034 "Intended Use of CAD Output"	4003
>>>	CONTAINS	CODE	(111059, DCM, "Single Image Finding")	GENERATED	See Table N.10-3	4006
>>>>	HAS CONCEPT MOD	CODE	(111056, DCM, "Rendering Intent")	GENERATED	See CID 6034 "Intended Use of CAD Output"	4006
>>>>	HAS PROPERTIES	TEXT	(111001, DCM, "Algorithm Name")	GENERATED		4019
>>>>	HAS PROPERTIES	TEXT	(111003, DCM, "Algorithm Version")	GENERATED		4019
>>>>	HAS PROPERTIES	SCOORD	(111010, DCM, "Center")	GENERATED		4021
>>>>>	R-SELECTED FROM	IMAGE		GENERATED		4021
>>>>	HAS PROPERTIES	SCOORD	(111041, DCM, "Outline")	GENERATED		4021
>>>>>	R-SELECTED FROM	IMAGE		GENERATED		4021
>>>	CONTAINS	CODE	(111059, DCM, "Single Image Finding" )	GENERATED	(129715009, SCT, "Breast Composition")	4006
>>>>	HAS CONCEPT MOD	CODE	(111056, DCM, "Rendering Intent")	GENERATED	See CID 6034 "Intended Use of CAD Output"	4006
>>>>	HAS PROPERTIES	TEXT	(111001, DCM, "Algorithm Name")	GENERATED		4019
>>>>	HAS PROPERTIES	TEXT	(111003, DCM, "Algorithm Version")	GENERATED		4019
>>>	HAS PROPERTIES	CODE	(129715009, SCT, "Breast Composition")	GENERATED	See DCID 6000, "Overall Breast Composition"	4007
>	CONTAINS	CODE	(111064, DCM, "Summary of Detections")	GENERATED	See CID 6042 "Status of Results"	4000
>>	INFERRED FROM	CONTAINER	(111063, DCM, "Successful Detections")	GENERATED		4015
>>>	CONTAINS	CODE	(111022, DCM, "Detection Performed")	GENERATED	See Table N.10-3	4017
>>>>	HAS PROPERTIES	TEXT	(111001, DCM, "Algorithm Name")	GENERATED		4019
>>>>	HAS PROPERTIES	TEXT	(111003, DCM, "Algorithm Version")	GENERATED		4019
>>>>>	R-SELECTED FROM	IMAGE		GENERATED		4021
>	CONTAINS	CODE	(111065, DCM, "Summary of Analyses")	GENERATED	See DICID 6042, "Status of Results"	4000
>>	INFERRED FROM	CONTAINER	(111062, DCM, "Successful Analyses")	GENERATED		4016
>>>	CONTAINS	CODE	(111004, DCM, "Analysis Performed")		See CID 6043, "Types of Mammography CAD Analysis"	4018
>>>>	HAS PROPERTIES	TEXT	(111001, DCM, "Algorithm Name")	GENERATED		4019
>>>>	HAS PROPERTIES	TEXT	(111003, DCM, "Algorithm Version")	GENERATED		4019
>>>>>	R-HAS PROPERTIES	IMAGE		GENERATED		4021

N.10.1.1 A.B.1.1 Code Sets

The following tables list specific code sets referenced from the Mammography CAD SR (TID 4000).

Table N.10-2. Mammography CAD SR - Image View Modifier Codes

Coding Scheme Designator	Code Value	Code Meaning
SCT	399161006	Cleavage
SCT	399011000	Axillary Tail
SCT	399197002	Rolled Lateral
SCT	399226006	Rolled Medial
SCT	414493004	Rolled Inferior
SCT	415670009	Rolled Superior

Table N.10-3. Mammography CAD SR - Single Image Finding Codes

Coding Scheme Designator	Code Value	Code Meaning
SCT	129793001	Mammography breast density
SCT	129770007	Individual Calcification
SCT	129769006	Calcification Cluster

N.10.2 A.B.2 Echocardiography Procedure Result SR (TID 5200)

Table N.10-4 shows the encoding of content of a DICOM Echocardiography Procedure Report (TID 5200).

[Table N.10-4 shows how to document TID content usage, with TID 5200 as an example." Modify to match your product implementation, e.g., select supported concepts and Values, and add additional templates as needed.]

Table N.10-4. Echocardiography Procedure Report SR (TID 5200)

NL	Rel with Parent	VT	Concept Name	Source	Values	TID	Comments
		CONTAINER	EV (125200, DCM, "Adult Echocardiography Procedure Report")			5200
>	HAS CONCEPT MOD	CODE	(121049, DCM, "Language of Content Item and Descendants")	CONFIGURATION	(en, RFC3066, "English" )	1204
>>	HAS CONCEPT MOD	CODE	(121046, DCM, "Country of Language" )	CONFIGURATION	(US, ISO3166_1, "United States of America (the) " )	1204
>	HAS OBS CONTEXT	CODE	(121005, DCM, "Observer Type")	GENERATED	(121006, DCM, "Person")	1002
>	HAS OBS CONTEXT	PNAME	EV (121008, DCM, "Person Observer Name")	CONFIGURATION		1003
>	CONTAINS	CONTAINER	EV (121118, DCM, "Patient Characteristics"	GENERATED		5201
>>	CONTAINS	NUM	(121118, DCM, "Subject Age")	GENERATED		5201	Calculated from Date of Birth
>>	CONTAINS	CODE	EV (121032, DCM, "Subject Sex")	MWL	See CID 7455 "Sex"	5201
>>	CONTAINS	NUM	(8277-6, LN, "Body Surface Area")	GENERATED		5201
>>>	INFERED FROM	CODE	(8278-4, LN, "Body Surface Area Formula")	GENERATED	See CID 3663 "Body Surface Area Equations"	5201
>	CONTAINS	CONTAINER	(59776-5, LN, "Findings")	GENERATED	One Container for each supported Finding Site, see Section N.10.2.1	5202
The following rows are supported for all Finding Sites listed in Section N.10.2.1. Values for supported concepts are listed in the "Modifier" column of the Tables in the respective subsections of Section N.10.2.1.
>>	HAS CONCEPT MOD	CODE	(363698007, SCT "Finding Site"	GENERATED	See TID 5200 for supported Finding Sites	5202
>>	CONTAINS	CONTAINER	(125007, DCM, "Measurement Group)			5202
>>>	CONTAINS	NUM	See Section N.10.2.1 for measurements and supported Modifiers for each Finding Site			300
>>>>	HAS CONCEPT MOD	CODE	(370129005, SCT, "Measurement Method")	GENERATED	See CID 12227 "Echocardiography Measurement Method"	300
>>>>	HAS CONCEPT MOD	CODE	(363698007, SCT, "Finding Site")	GENERATED	See CID 12236 "Echo Anatomic Sites"	300
>>>>	HAS CONCEPT MOD	CODE	(26067400, SCT, "Flow Direction")	GENERATED	See CID 12221 "Flow Direction"	5203
>>>>	HAS CONCEPT MOD	CODE	(272517003, SCT, "Respiratory Cycle Point")	GENERATED	See CID 12234 "Respiration State"	5203
>>>>	HAS CONCEPT MOD	CODE	(272518008, SCT, "Cardiac Cycle Point")	GENERATED	See CID 12233 "Cardiac Phase"	5203
>>>>	HAS CONCEPT MOD	CODE	(399264008, SCT, "Image Mode")	GENERATED	See CID 12224 "Ultrasound Image Modes"	5203
>>>>	HAS CONCEPT MOD	CODE	(111031, DCM, "Image View")	GENERATED	See CID 12002 "Ultrasound Protocol Stage Types"	5203

N.10.2.1 A.B.2.1 Measurement Encoding

The following Sections provide a list of measurements encoded for each Finding Site.

[Since the lists of measurements can be fairly extensive, they can either be provided in a separate excel sheet minimally providing columns for

Label
The encoding of the measurement using Coding Scheme Designator, Code Value and Code Meaning
One column for each supported modifier (Image Mode, Image View, Measurement Method, Cardiac Cycle Point, …)
The unit code for the measurement using Coding Scheme Designator, Code Value and Code Meaning.]

[If you use an external document, state the following:]

Details about the supported measurements can be found at <link to external document>.

[If measurements are documented in this document, add for each supported Finding Site a subsection with all supported Measurements and their modifiers below following the examples shown.]

N.10.2.1.1 A.B.2.1.1 Left Ventricle

Table N.10-5 lists the measurements supported by <product>. The first column lists the label that is used on <products reporting screen>to select the respective measurements.

[Document all measurements supported on the product using the relevant measurements. Modify to match your product implementation, e.g., select supported concepts and Values, and add additional templates as needed. If private codes are used, indicate them through a 99_VENDOR_X Coding Scheme Designator, where VENDOR_X needs to be replaced with a vendor specific Value.]

[In the "Modifier" column list all supported modifiers by using the Concept Name Code from Table N.10-4 in Section N.10.2 and add a code for each Modifier Value.]

Table N.10-5. Left Ventricle Measurements

Label	Measurement	Modifier		Unit
Echo Section (TID 5202) - Left Ventricle, (363698007, SCT, "Finding Site") : (87878005, SCT, " Left Ventricle")
LV CI A2C MOD	(54993008, "SCT, Cardiac Index")	(399264008, SCT, "Image Mode")	(399064001, SCT, "2D mode")	(l/min/m2, UCUM, "l/min/m2")
		(111031, DCM, "Image View")	(399232001, SCT, "Apical two chamber")
		(370129005, SCT, "Measurement Method")	(125208, DCM, "Method of Disks, Single Plane")
LVID d PSAX A-P	(LVID_AP, 99VENDOR_X, Left Ventricle Internal Dimension A-P")	(272518008, SCT, "Cardiac Cycle Point")	(90892000, SCT, "Diastole")	(l/min/m2, UCUM, "l/min/m2")
	(111031, DCM, "Image View")		(399271003, SCT, "Parasternal short axis at the Papillary Muscle level")
	(399264008, SCT, "Image Mode")		(399064001, SCT, "2D mode")
…

N.10.2.1.2 A.B.2.1.2 Right Ventricle

Table N.10-6 list the measurements supported by <product>. The first column lists the label that is used on <products reporting screen>to select the respective measurements.

Table N.10-6. Right Ventricle Measurements

Label	Measurement	Modifier		Unit
Echo Section (TID 5202) - Right Ventricle, (363698007, SCT, "Finding Site") : (53085002, SCT, "Right Ventricle")
RV Area s A4C	(42798000, SCT "Area")	(272518008, SCT, "Cardiac Cycle Point")	(111973004, SCT, "Systole")	(cm2/m2, UCUM, "cm2/m2")
		(111031, DCM, "Image View")	(399214001, SCT "Apical four chamber")
		(399264008, SCT, "Image Mode")	(399064001, SCT, "2D mode")
		(370129005, SCT, "Measurement Method")	(125208, DCM, "Method of Disks, Single Plane")
…

N.11 A.C Security Details

[This section contains several subsections that describe information that may already be present in other security documents (e.g., MDS2 statement). For each subsection, you may fill it in or remove it and reference a separate security document if all information requested in this template is present in the separate referenced document.]

This section provides additional details about security features that are formally described in Section N.8.

N.11.1 A.C.1 External Network Requirement Details

N.11.1.1 A.C.1.1 Basic Time Synchronization

[If your product is following RFC 8633, mention it here, otherwise describe what is implemented, e.g.:

If your product is able to perform the Find NTP Servers Transaction using DCP when no server has been found through use of NTP, then describe it here.
State here what the product does if no NTP Servers are available or reference the product manual section describing what to do in such a case.]

N.11.1.2 A.C.1.2 Basic Network Address Management

[If this application supports the Basic Network Address Management profile as a DHCP Client, specify here how the DHCP Server is discovered.

If DNSSEC is supported (RFC 4033, RFC 4034, RFC 4035) for the interactions defined in Basic Network Address Management profile, describe the options supported here or provide a reference to the document describing them.]

N.11.1.3 A.C.1.3 Application Configuration Management

Table N.11-1 defines the security patterns supported :

[Specify here which security pattern(s) your LDAP Client and/or LDAP Server implementation supports. Remove any actor not supported.]

Table N.11-1. LDAP Security Patterns

Actor	LDAP Security Pattern	Supported	Comments
LDAP Server	TLS
	TLS-Manual
	Basic
	Basic-Manual
	Anonymous
	Anonymous-Manual
	[Additional pattern]
LDAP Client	TLS
	TLS-Manual
	Basic
	Basic-Manual
	Anonymous
	Anonymous-Manual
	[Additional pattern]

N.11.1.4 A.C.1.4 DNS Service Discovery

[If DNSSEC is supported (RFC 4033, RFC 4034, RFC 4035) for the interactions to achieve DNS Service Discovery, describe the options supported here or provide a reference to the document describing them.]

N.11.2 A.C.2 DICOM Security Profile Details

N.11.2.1 A.C.2.1 Online Electronic Storage Secure Use

[Indicate here how the product restricts remote access (User Access, Access per Patient, Access per Doctor). If this information is described in a separate document, provide the reference here instead.]

N.11.2.2 A.C.2.2 Audit Trail Messages

Table N.11-2 specifies the DICOM Audit Messages that <Product> can detect and report. It defines the list of triggers that will cause the Audit Message to be generated and if these triggers can be configured or not. It also specifies whether the content of the Audit Message can be configured or not.

[Indicate with Y (yes) or N (no) in the "Used" column to specify if your product supports the Audit Message. Then describe the list of triggers in the "Supported Triggers" column that make your product generate the Audit Message. Indicate with Y or N in the "Configurable Triggers" or "Configurable Message" columns whether these features are supported by your product.]

Table N.11-2. DICOM Specific Audit Messages

Audit Message	Used	Supported Triggers	Configurable Triggers	Configurable Message	Comments
Application Activity
Audit Log Used
Begin Transferring DICOM Instances
Data Export
Data Import
DICOM Instance Accessed
DICOM Instance Transferred
DICOM Study Deleted
Network Entry
Query
Security Alert
User Authentication
Order Record
Patient Record
Procedure Record
[Other Message]

[The following part of this section can be either defined in the DCS or defined as a reference to a Service/Security Manual instead. In either case, all private messages will be described in addition to standard defined messages. As an example, the following table format may be used to describe these messages in this document.]

Table N.11-3 specifies the implementation details of each audit message supported by this product.

Table N.11-3. Audit Message Details

Real-World Entities	Field Name	Supported	Value Constraints
Application Activity Message
Event	EventID		EV (110100, DCM, "Application Activity")
	EventActionCode
	EventDateTime
	EventOutcomeIndicator
	EventTypeCode
Active Participant: Application started (1)	UserID
	AlternativeUserID
	UserName
	…
…	…	…	…
[Any extension]	…	…	…
Audit Log Used Message
…	…	…	…

…
[Other message]

N.11.2.3 A.C.2.3 Audit Trail Message Transmission Profile - SYSLOG - TLS

See Section N.6.6 Audit Trail Syslog Configuration for information about Syslog-TLS parameters.

N.11.2.4 A.C.2.4 Audit Trail Message Transmission Profile - SYSLOG - UDP

See Section N.6.6 Audit Trail Syslog Configuration for information about Syslog-UDP parameters.

N.11.2.5 A.C.2.5 Secure Transport Connection Details

Table N.11.2.5-1 lists the secure transport connection profiles and cipher suites supported for TLS 1.3:

[Describe here the mechanisms and tools that are supported by the implementation for Certificate Distribution, Certificate Validation and Key Management.]

[In Table N.11.2.5-1 Secure Transport Connection Profiles and Cipher Suites, add any Profile claimed in Section N.8.4.2 Secure Transport Connection Profiles. For each Profile, list all TLS 1.3 Cipher suites supported by your product and fill in the "Default Preference Order" column if applicable.]

Table N.11.2.5-1. Secure Transport Connection Profiles and Cipher Suites

Profile	Cipher Suite	Default Preference Order (from 1=preferred to n=less preferred)
Modified BCP 195 RFC 8996 TLS Secure Transport Connection Profile	TLS_AES_256_GCM_SHA384
	TLS_CHACHA20_POLY1305_SHA256
	TLS_AES_128_GCM_SHA256
	TLS_AES_128_GCM_SHA256
	TLS_AES_128_CCM_8_SHA256
[Any TLS Profile supported by <product>]	[Any Cypher suite]

Table N.11.2.5-2 lists the secure transport connection profiles and key exchange algorithms supported for TLS 1.3:

[In Table N.11.2.5-2 Secure Transport Connection Profiles and TLS 1.3 Key Exchange Algorithms, add any Profile claimed in Section N.8.4.2 Secure Transport Connection Profiles. For each Profile, list all TLS 1.3 key exchange algorithms supported by your product and fill in the “Default Preference Order” column if applicable]

Table N.11.2.5-2. Secure Transport Connection Profiles and TLS 1.3 Key Exchange Algorithms

Profile	Key Exchange Algorithms	Default Preference Order (from 1=preferred to n=less preferred)
Modified BCP 195 RFC 8996 TLS Secure Transport Connection Profile	ECDHE
	DHE
[Any TLS Profile supported by <product>]	[Any key exchange algorithm]

Table N.11.2.5-3 lists the secure transport connection profiles and signature algorithms supported for TLS 1.3:

[In Table N.11.2.5-3 Secure Transport Connection Profiles and TLS 1.3 Signature Algorithms, add any Profile claimed in Section N.8.4.2 Secure Transport Connection Profiles. For each Profile, list all TLS 1.3 signature algorithms supported by your product and fill in the “Default Preference Order” column if applicable]

Table N.11.2.5-3. Secure Transport Connection Profiles and TLS 1.3 Signature Algorithms

Profile	Signature Algorithms	Default Preference Order (from 1=preferred to n=less preferred)
Modified BCP 195 RFC 8996 TLS Secure Transport Connection Profile	ECDSA
	RSASSA PKCS#1 v1.5 (RSA)
	RSASSA-PSS
[Any TLS Profile supported by <product>]	[Any signature algorithm]

Table N.11-4 lists the secure transport connection profiles and cipher suites supported for TLS 1.2:

[In Table N.11-4, add any Profile claimed in Section N.8.4.2 Secure Transport Connection Profiles. For each Profile, list all TLS 1.2 Cipher suites supported by your product and fill in the "Default Preference Order" column if applicable.]

Table N.11-4. Secure Transport Connection Profiles and Cipher Suites

Profile	Cipher Suite	Default Preference Order (from 1=preferred to n=less preferred)
Modified BCP 195 RFC 8996 TLS Secure Transport Connection Profile	TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	TLS_ECDHE_ECDSA_WITH_CAMELLIA_256_GCM_SHA384
	TLS_ECDHE_RSA_WITH_CAMELLIA_256_GCM_SHA384
	TLS_ECDHE_ECDSA_WITH_AES_256_CCM
	TLS_ECDHE_ECDSA_WITH_AES_256_CCM_8
	TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
	TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
	TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
	TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
	TLS_ECDHE_ECDSA_WITH_CAMELLIA_128_GCM_SHA256
	TLS_ECDHE_RSA_WITH_CAMELLIA_128_GCM_SHA256
	TLS_ECDHE_RSA_WITH_CAMELLIA_128_GCM_SHA256
	TLS_ECDHE_ECDSA_WITH_AES_128_CCM_8
	[Other Cipher Suites]
[Any TLS Profile supported by <product>]	[Any Cypher suite]

[Describe here the mechanisms and tools that are supported by the implementation for Certificate Distribution, Certificate Validation and Key Management.]

Table N.11-5 describes the configurable parameters and behaviors supported by this product for the Secure Transport Connection:

[Indicated in the "Configurable" column whether the parameters are configurable (Y) or not (N).]

Table N.11-5. Secure Transport Connection Configuration

Local Secure Transport Connection Configuration
Parameter/Behavior	Configurable	Default Value	Comments
Common Secure Transport Connection parameters
Port	See Section N.6 Configuration
A-P-ABORT provider reason in case of integrity check failure
…	…
BCP 195 RFC 8996 TLS Secure Transport Connection
[List specific configurable parameters for the local system]

Modified BCP 195 RFC 8996 TLS Secure Transport Connection Parameters
[List specific configurable parameters for the local system]

Other Profile Secure Transport Connection parameters

Remote Secure Transport Connection Configuration Parameters
Parameter	Configurable	Default Value	Comments
Common Secure Transport Connection Parameters
Port	See Section N.6 Configuration
A-P-ABORT provider reason in case of integrity check failure
…	…
BCP 195 RFC 8996 TLS Secure Transport Connection
[List specific configurable parameters for the local system]

Modified BCP 195 RFC 8996 TLS Secure Transport Connection Parameters
[List specific configurable parameters for the local system]

<Other Profile> Secure Transport Connection Parameters

N.11.2.6 A.C.2.6 Attribute Confidentiality Details

Table N.11-6 provides the list of Attributes and the action when de-identifying instances. Supported Action Codes are defined in PS 3.15 Section E.1.

[For every element listed in Table N.11-6, “De-identified Elements and Actions”, describe the Action the application may take using one of the actions codes defined below:]

D: replace with a non-zero length Value that may be a dummy Value and consistent with the VR
Z: replace with a zero-length Value, or a non-zero length Value that may be a dummy Value and consistent with the VR
X: remove
K: keep (unchanged for non-sequence Attributes, cleaned for sequences)
C: clean, that is replace with Values of similar meaning known not to contain identifying information and consistent with the VR
U: replace with a non-zero length UID that is internally consistent within a set of Instances
Z/D: Z unless D is required to maintain IOD conformance (Type 2 versus Type 1)
X/Z: X unless Z is required to maintain IOD conformance (Type 3 versus Type 2)
X/D: X unless D is required to maintain IOD conformance (Type 3 versus Type 1)
X/Z/D: X unless Z or D is required to maintain IOD conformance (Type 3 versus Type 2 versus Type 1)
X/Z/U*: X unless Z or replacement of contained instance UIDs (U) is required to maintain IOD conformance (Type 3 versus Type 2 versus Type 1 sequences containing UID references)

[Indicated in the "Encrypted" column, whether encryption is supported. Y for yes, N for No.]

Table N.11-6. De-identified Elements and Actions

Attribute Name	Tag	Comments
Basic Profile Option
<Element name>	<(xxxx,yyyy) >	[In case of dummy Value, describe here the algorithm that produces the Value]



[Additional Private Option]

[Explain the scope here in which the application can ensure referential integrity of replacement Values for references such as SOP Instance UID, Frame of Reference UID, etc. if multiple SOP Instances are de-identified (e.g., across multiple Studies, consistent replacement if the same Study is processed more than once, etc.)

Also mention if Encrypted Attributes Data Set is to be used and which Transfer Syntaxes are supported for encoding/decoding the Encrypted Attributes Data Set.

Finally, list here any additional restrictions (e.g., key sizes for public keys).]

N.11.2.7 A.C.2.7 Digital Signature Details

[Describe here the details of any Digital Signature Profile that your product may support. Put "N/A" if none.]

N.11.2.8 A.C.2.8 Additional DICOM Security Profile Details

[Describe here the details of any additional DICOM Security Profile that your product may support. Put "N/A" if none.]

N.12 A.D Mapping of Attributes

[Describe the Mapping of Attributes in this Annex, create a subsection for each mapping. Examples for such mappings are:

The mapping of the HL7 Order information into the return keys of the Modality Worklist query
The mapping between Modality Worklist, Instances and MPPS messages
The mapping between DICOM SR instances and reports in CDA format]

[The following subsection shows an example for the Mapping between Modality Worklist Instances and MPPS.]

N.12.1 A.D.1 Mapping Between Modality Worklist Instances and MPPS

Table N.12-1 describes the mapping of Attributes between Modality Worklist Instances and MPPS messages.

In the "Scenario" column the following Values are used:

[List the different scenarios which your product supports for mapping Attributes and use those Values in Table N.12-1 in the "Scenario" column. The list below represents an example that is derived from the IHE Radiology Technical Framework - Vol. 2; however, you can define your own scenarios or modify the list below. All entries in the list need to occur as permanent text in your DICOM Conformance Statement.]

SCHEDULED: The image acquisition was scheduled at the RIS and procedure details have been communicated in the MWL query)
UNSCHEDULED: The image acquisition was performed without Modality Worklist information
APPEND: Instances acquired are added to an existing study after the initial procedure was finalized
GROUP: Multiple requested procedures are grouped into one study.

In the "Value Source" columns, the following Values are used. The column cell may additionally contain an Attribute Tag if the value is copied from a different Attribute.

GENERATED: The Value is generated by the system.
SRC_INSTANCE: The Value is copied from previously created instances.
MWL: The Value is copied from a Modality Worklist entry.
USER: The Value is entered by the user.
SCANNED: The Value is read from a barcode scanner or similar device.
EMPTY: The Attribute is sent with a zero-length Value.

The "Destination" columns either contain TOP, if the Attribute is added to the top level Data Set of the Instance, or contain the Attribute Tag of the Sequence the Attribute will be added to. The "Comments" column can be used to provide additional information regarding the Values added to the Instance or MPPS.

[Update Table N.12-1 to match your product implementation. The entries in the table are meant as an example.]

Table N.12-1. Mapping of Attributes from Modality Worklist to Instance and MPPS

Attribute Name in Image/MPPS	Tag	Scenario	Image		MPPS		Comments
Attribute Name in Image/MPPS	Tag	Scenario	Value Source	Destination	Value Source	Destination	Comments
Study Instance UID	(0020,000D)	SCHEDULED	MWL	TOP	SRC_INSTANCE	(0040,0270)
		UNSCHEDULED	GENERATED	TOP	EMPTY	(0040,0270)
		APPEND	SRC_INSTANCE	TOP	SRC_INSTANCE	(0040,0270)
		GROUP	SYSTEM	TOP	SRC_INSTANCE	(0040,0270) ^(a)	^(a) One item per SPS in (0040, 0270)
Accession Number	(0008,0050)	SCHEDULED	MWL	TOP	SRC_INSTANCE	(0040,0270)
		UNSCHEDULED	EMPTY	TOP	EMPTY	(0040,0270)
		APPEND	SRC_INSTANCE	TOP	SRC_INSTANCE	(0040,0270)
		GROUP	MWL;EMPTY ^(a)	TOP	MWL ^(b)	(0040,0270)	^(a) If the Accession Number for all Requested Procedures is the same, use that in the Accession Number of the Instances. If different keep empty. ^(b) Copy Accession Number for each Requested Procedure into the item of the appropriate SPS.
Requested Procedure ID	(0040,1001)	SCHEDULED	MWL	(0040,0275) ^(a) (0040,A370) ^(b)	SRC_INSTANCE	(0040,0270)	^(a) for use in Image IODs ^(b) for use in Evidence Documents
		UNSCHEDULED	N/A	N/A	EMPTY	(0040,0270)
		APPEND	SRC_INSTANCE	(0040,0275) ^(a) (0040,A370) ^(b)	SRC_INSTANCE	(0040,0270)	^(a) for use in Image IODs ^(b) for use in Evidence Documents
		GROUP
Study ID	(0020,0010)	SCHEDULED	MWL (0040,1001)	TOP	SRC_INSTANCE	TOP	(0040,1001) is Requested Procedure ID
		UNSCHEDULED	GENERATED	TOP	SRC_INSTANCE	TOP
		APPEND	SRC_INSTANCE (0040,1001)	TOP	SRC_INSTANCE	TOP	(0040,1001) is Requested Procedure ID

N.13 A.E Code Set Usage

[This subsection is used to describe code set usage such as:

Handling of local procedure codes
Handling of local formulary and drug codes
Handling of retired or no longer used codes and code sets
- Handling of the use of SNOMED RT vs SNOMED CT codes
Handling of private codes
Definition of vendor private codes

]